Check-Host.cc

Domain

megalinkshare.website

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of megalinkshare.website

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
4
A/AAAA targets
Subdomains
4
CT + scan + body
Record Types
3
seen in DNS
Observed Certs
6
in our scans

DNS Records

A
104.21.1.173, 172.67.129.169
AAAA
2606:4700:3032::ac43:81a9, 2606:4700:3035::6815:1ad
MX
NS
bingo.ns.cloudflare.com, kai.ns.cloudflare.com
TXT
CNAME
CAA

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

47.128.172.106:443 href · ×602
16.79.23.28:443 href · ×7
13.251.70.248:443 href · ×7
16.79.23.28:80 href · ×7
108.137.187.210:443 href · ×5
13.213.191.42:443 href · ×2
3.79.236.213:443 href · ×2
13.213.217.229:443 href · ×2
18.136.167.98:443 href · ×2
54.169.73.112:443 href · ×2
54.179.144.218:80 href · ×2
52.74.223.116:443 href · ×2
52.60.200.227:443 href · ×2
18.142.143.178:443 href · ×2
13.228.154.239:80 href · ×2
54.251.155.64:80 href · ×2
52.76.27.76:443 href · ×2
3.96.185.196:443 href · ×2
122.248.214.116:443 href · ×2
15.157.251.74:443 href · ×1
15.156.231.50:443 href · ×1
54.81.125.214:443 href · ×1
54.251.242.218:443 href · ×1

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
A 104.21.1.173 2026-05-26 07:07:02.960 2026-06-20 16:04:47.095
NS bingo.ns.cloudflare.com 2026-05-26 07:07:02.960 2026-06-22 02:50:39.496
AAAA 2606:4700:3035::6815:1ad 2026-05-26 07:07:02.960 2026-06-20 16:04:47.095
A 172.67.129.169 2026-05-26 07:07:02.960 2026-06-20 16:04:47.095
AAAA 2606:4700:3032::ac43:81a9 2026-05-26 07:07:02.960 2026-06-20 16:04:47.095
NS kai.ns.cloudflare.com 2026-05-26 07:07:02.960 2026-06-22 02:50:39.496