CONTINUOUS INTERNET TELEMETRY24H DRIFT31,420 material changesacross 29,745 domains · last 24hSHIFT20 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,183 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,263 sites429 rate-limit / 403 bot-block, a posture signal

victorianshipmodels.com

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

This reading of victorianshipmodels.com was taken 1d ago

victorianshipmodels.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting victorianshipmodels.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 victorianshipmodels.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
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-02 21:20 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 victorianshipmodels.com actually stands on - every host below is a signed observation
victorianshipmodels.com
A / AAAA
185.151.30.205
unattributedserves the site
NS
ultra103.uk2.netultra104.uk2.net
uk2.netanswers its DNS
MX
uk2mxarray1.uk2.net
uk2.netreceives its email

DNS Records

A 1

  • 185.151.30.205

MX 1

  • 0uk2mxarray1.uk2.net

TXT 1

  • v=spf1 include:_spf.hostedemail.com ~all

NS 2

  • ultra103.uk2.net
  • ultra104.uk2.net

SOA 1

  • ultra103.uk2.net hostmaster\@victorianshipmodels.com

MCP_RECORDS 1

  • v=spf1 include:_spf.hostedemail.com ~all

DMARC_RECORDS 1

  • v=spf1 include:_spf.hostedemail.com ~all

BIMI_RECORDS 1

  • v=spf1 include:_spf.hostedemail.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.hostedemail.com ~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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_32762caaa293fa18
Output Hash
498c09ce5ef8dd3f3e16ca795734ef9d6abc3cd960a47ba0ddc21fa039494914
Signature
ed25519:d83043e84de97ac0c8200d9b51ccfd5c49ce685efab4dda1ed5c2a3ba53357bc52dc9ff7d60f5eab8f7ca54bc4c71055a322d840e8eb4a39bdd68f83e073dd04
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser