CONTINUOUS INTERNET TELEMETRY24H DRIFT43,686 material changesacross 39,414 domains · 24h to ~50m ago · +9,069 vs yesterdaySHIFT37 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW542 curated domains not reachablelast probe, steadySITE ERRORS33,822 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 151,367 sites429 rate-limit / 403 bot-block, a posture signal

visahq.pk

Observed Aug 2, 2026, 11:02 UTC (3d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of visahq.pk was taken 3d ago

visahq.pk is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting visahq.pk under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch visahq.pk Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byGoogle (SPF sender)
Secured byLet's Encrypt
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 03:06 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat visahq.pk actually stands on - every host below is a signed observation
visahq.pk
A / AAAA
34.233.200.138
unattributedserves the site
NS
ns1.3oha.comns2.3oha.com
3oha.comanswers its DNS
MX
mail.visahq.com
Google (SPF sender)receives its email
TLS
visahq.pk
Let's Encryptissued its certificate

DNS Records

A 1

  • 34.233.200.138

MX 1

  • 0mail.visahq.com

TXT 1

  • v=spf1 a mx ip4:63.219.179.224/27 ip4:176.223.109.0/25 ip4:162.210.199.64/27 ip4:54.251.101.143 ip4:170.75.163.206 include:amazonses.com include:_spf.google.com include:spf.mandrillapp.com include:spf.mail.intercom.io include:zoho.com -all

NS 2

  • ns1.3oha.com
  • ns2.3oha.com

SOA 1

  • ns1.3oha.com oleg.visahq.com

MCP_RECORDS 1

  • v=spf1 a mx ip4:63.219.179.224/27 ip4:176.223.109.0/25 ip4:162.210.199.64/27 ip4:54.251.101.143 ip4:170.75.163.206 include:amazonses.com include:_spf.google.com include:spf.mandrillapp.com include:spf.mail.intercom.io include:zoho.com -all

DMARC_RECORDS 1

  • v=spf1 a mx ip4:63.219.179.224/27 ip4:176.223.109.0/25 ip4:162.210.199.64/27 ip4:54.251.101.143 ip4:170.75.163.206 include:amazonses.com include:_spf.google.com include:spf.mandrillapp.com include:spf.mail.intercom.io include:zoho.com -all

BIMI_RECORDS 1

  • v=spf1 a mx ip4:63.219.179.224/27 ip4:176.223.109.0/25 ip4:162.210.199.64/27 ip4:54.251.101.143 ip4:170.75.163.206 include:amazonses.com include:_spf.google.com include:spf.mandrillapp.com include:spf.mail.intercom.io include:zoho.com -all

MTA_STS_RECORDS 1

  • v=spf1 a mx ip4:63.219.179.224/27 ip4:176.223.109.0/25 ip4:162.210.199.64/27 ip4:54.251.101.143 ip4:170.75.163.206 include:amazonses.com include:_spf.google.com include:spf.mandrillapp.com include:spf.mail.intercom.io include:zoho.com -all

TLS Certificates (3)

Common NameIssuerExpires
visahq.pk C=US, O=Let's Encrypt, CN=YR1 Fri, 30 Oct 2026 15:10:14 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (0)

None observed.

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_cb0c7c2cec52b8a5
Output Hash
92d38bcf8b1a51317f6a83430fa4216612aba404a6716783728b716cd0c20d15
Signature
ed25519:1f8c7d68d5d2d67ecb34a8d7b994bd6811b153bbb482d02e14c060c31e541edd04c8bc8c5a5fe063616254547b16e618688fc87d8467df9dc2aa7fd344c0b90c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser