kamkor.me

Observed Aug 16, 2026, 17:31 UTC (5h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Not responding
Signed observation on record.
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-16 17:31 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 kamkor.me actually stands on - every host below is a signed observation
kamkor.me
A / AAAA
213.189.55.194
unattributedserves the site
NS
dns1.mydevil.netdns2.mydevil.net
mydevil.netanswers its DNS
MX
mail4.mydevil.net
mydevil.netreceives its email

DNS Records

A 1

  • 213.189.55.194

MX 1

  • 10mail4.mydevil.net

TXT 1

  • v=spf1 ?include:mail4.mydevil.net a mx -all

NS 2

  • dns1.mydevil.net
  • dns2.mydevil.net

SOA 1

  • dns1.mydevil.net admin.admin.net.pl

MCP_RECORDS 1

  • v=spf1 ?include:mail4.mydevil.net a mx -all

DMARC_RECORDS 1

  • v=spf1 ?include:mail4.mydevil.net a mx -all

BIMI_RECORDS 1

  • v=spf1 ?include:mail4.mydevil.net a mx -all

MTA_STS_RECORDS 1

  • v=spf1 ?include:mail4.mydevil.net a mx -all

TLS Certificates (0)

None.

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_7527b3a6c2231840
Output Hash
59ca5071811e8a5fc69220df83c654de1dfd3e222a94937e4a231320f302ea47
Signature
ed25519:c14ffaf34f2314fb9e42bc92c85bbf9bd5ea5f05e474aee7e6f08ac3aff7033330225a43e8c30d7de5d0ffa541657523cc0c6d3bf90c0b9abc857010d3a42204
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT41,073 material changesacross 39,134 domains · 24h to ~2h ago · -486 vs yesterdayROTATION61 domains moved DNS from koaladns.com to magpiedns.com, 59 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email provider24hNOW593 curated domains not reachable+98 vs yesterdaySITE ERRORS35,566 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,265 sites429 rate-limit / 403 bot-block, a posture signal