maytail.jp

Observed Aug 12, 2026, 04:56 UTC (4d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of maytail.jp was taken 4d ago

maytail.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting maytail.jp 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 maytail.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
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-15 05:16 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 maytail.jp actually stands on - every host below is a signed observation
maytail.jp
A / AAAA
103.37.111.180
unattributedserves the site
NS
ns1.value-domain.comns2.value-domain.com
value-domain.comanswers its DNS
MX
maytail.jp
maytail.jpreceives its email
TLS
maytail.jp
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.37.111.180

MX 1

  • 10maytail.jp

TXT 1

  • v=spf1 include:spf.s-pf.jp a:maytail.jp ~all

NS 2

  • ns1.value-domain.com
  • ns2.value-domain.com

SOA 1

  • ns1.value-domain.com hostmaster.maytail.jp

MCP_RECORDS 1

  • v=spf1 include:spf.s-pf.jp a:maytail.jp ~all

DMARC_RECORDS 1

  • v=spf1 include:spf.s-pf.jp a:maytail.jp ~all

BIMI_RECORDS 1

  • v=spf1 include:spf.s-pf.jp a:maytail.jp ~all

MTA_STS_RECORDS 1

  • v=spf1 include:spf.s-pf.jp a:maytail.jp ~all

TLS Certificates (3)

Common NameIssuerExpires
maytail.jp C=US, O=Let's Encrypt, CN=YR1 Sat, 12 Sep 2026 18:01:47 +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_2a379a855ab4d5bd
Output Hash
6d908b13cb7ea34dfe4cbff3635d95a9bde707607641631ad439e518c650a584
Signature
ed25519:c95db3bf18ec7fdceffb4c321f5a7c69557542774799c94c2d25303f13acfb20c7ea1aa58acb7408d695e268c2599a71827d2e61835bee39940c8f3215084602
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT44,916 material changesacross 42,981 domains · last 24h · +3,357 vs yesterdayROTATION62 domains moved DNS from magpiedns.com to koaladns.com, 58 moved backa rotation loop, not a migration · 24hNOW497 curated domains not reachablelast probe, steadySITE ERRORS36,283 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,423 sites429 rate-limit / 403 bot-block, a posture signal