botperu.com

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

This reading of botperu.com was taken 6d ago

botperu.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting botperu.com 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 botperu.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onDEFT
Secured byLet's Encrypt
Registered withInternet Domain Service BS Corp.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-15 21:39 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 botperu.com actually stands on - every host below is a signed observation
botperu.com
A / AAAA
216.246.46.43
DEFTserves the site
NS
ns2.botperu.comns1.botperu.com
botperu.comanswers its DNS
MX
botperu.com
botperu.comreceives its email
TLS
botperu.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 216.246.46.43

MX 1

  • 0botperu.com

TXT 1

  • v=spf1 +a +mx include:relay.mailchannels.net ~all

NS 2

  • ns2.botperu.com
  • ns1.botperu.com

SOA 1

  • ns1.botperu.com servers.privatednsorg.com

MCP_RECORDS 1

  • v=spf1 +a +mx +ip4:216.246.46.34 ~all

DMARC_RECORDS 1

  • v=spf1 +a +mx +ip4:216.246.46.34 ~all

BIMI_RECORDS 1

  • v=spf1 +a +mx +ip4:216.246.46.34 ~all

MTA_STS_RECORDS 1

  • v=spf1 +a +mx +ip4:216.246.46.34 ~all

TLS Certificates (3)

Common NameIssuerExpires
botperu.com C=US, O=Let's Encrypt, CN=YR2 Thu, 01 Oct 2026 03:04:01 +0000
YR2 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_fb9d14dca5360508
Output Hash
4707c378f09891f3132bd46139bf886e90c1737072a735ff741c28bbf6cda5ed
Signature
ed25519:393373df2143d0b0803dadbc4f7d54b4181995f98bfeffbd9ec574b2f450ca86ed797ced64900dc2c8631a96e402178ebde6d98652064b4341e66987f6e65107
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT40,574 material changesacross 38,742 domains · 24h to ~3h ago · -985 vs yesterdayROTATION62 domains moved DNS from magpiedns.com to koaladns.com, 60 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email provider24hNOW582 curated domains not reachable+87 vs yesterdaySITE ERRORS36,429 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,461 sites429 rate-limit / 403 bot-block, a posture signal