leadfamly.com
Observed Aug 3, 2026, 02:49 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.
leadfamly.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting leadfamly.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 leadfamly.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.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.
DNS Records
A 1
35.198.87.242
MX 4
1aspmx.l.google.com10aspmx2.googlemail.com5alt1.aspmx.l.google.com5alt2.aspmx.l.google.com
TXT 5
MS=24B96803E4DEC9D12F85D505FD4E6F288E87BBF3facebook-domain-verification=k4odt35ct30v00nkzpx4xpuijr86gegoogle-site-verification=dHZOOldV2Of7Nx78TnWiyYVoDQzTU4TuQeyAQXfNVhoil9mr5frn4n0q3t7spn92k1j1jv=spf1 include:_spf.google.com include:amazonses.com include:servers.mcsv.net include:spf-basic.fogcreek.com include:spf.rpost.net include:5169257.spf02.hubspotemail.net ip4:46.30.121.240 ip4:46.30.121.230 -all
NS 4
ns-1281.awsdns-32.orgns-1998.awsdns-57.co.ukns-671.awsdns-19.netns-91.awsdns-11.com
SOA 1
ns-1998.awsdns-57.co.uk awsdns-hostmaster.amazon.com
CAA 4
iodef "mailto:tech-services+caareport@playable.com"issue "amazon.com"issue "letsencrypt.org"issue "pki.goog"
MCP_RECORDS 1
v=spf1 include:leadfamly.com -all
DMARC_RECORDS 1
v=DMARC1;p=reject;pct=100;rua=mailto:dmarcreports@leadfamly.com;ruf=mailto:dmarc-forensic-reports@leadfamly.com
BIMI_RECORDS 1
v=spf1 include:leadfamly.com -all
MTA_STS_RECORDS 1
v=spf1 include:leadfamly.com -all
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
leadfamly.com |
C=US, O=Let's Encrypt, CN=YR2 | Mon, 12 Oct 2026 15:36:54 +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.
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 receiptEd25519 Receipt
- Receipt ID
rcpt_0f46d4233e019fe6- Output Hash
173b2ae271478340c4a3d79d2b56c2573d80d62bd439d7921abb1445b020135b- Signature
ed25519:8421cdf6dbad5894e804e40fe7e861ff60a1b1a8b7a5ff1d4a3ce6603000d48503042fc9a50777ef4e4b1bb824c4c2b97524a00696ea2d15eebba96f096c2403- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast