CONTINUOUS INTERNET TELEMETRY24H DRIFT48,244 material changesacross 46,548 domains · 24h to ~5h ago · +13,627 vs yesterdaySHIFT100 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW534 curated domains not reachablelast probe, steadySITE ERRORS33,821 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 135,269 sites429 rate-limit / 403 bot-block, a posture signal

urban.partners

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

This reading of urban.partners was taken 3d ago

urban.partners is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting urban.partners 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 urban.partners Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Email byMicrosoft 365
Secured byLet's Encrypt
Also usesAtlassian
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 04:28 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 urban.partners actually stands on - every host below is a signed observation
urban.partners
A / AAAA
216.150.1.1
unattributedserves the site
NS
ns1-06.azure-dns.comns2-06.azure-dns.netns3-06.azure-dns.orgns4-06.azure-dns.info
azure-dns.com + azure-dns.net + moreanswers its DNS
MX
urban-partners.mail.protection.outlook.com
Microsoft 365receives its email
TLS
urban.partners
Let's Encryptissued its certificate

DNS Records

A 1

  • 216.150.1.1

MX 1

  • 0urban-partners.mail.protection.outlook.com

TXT 6

  • 00DDn00000Atv6A=1TBUX00000009ph
  • lucid-verification=<pva@YWE0quk7wtw9vcx>
  • v=spf1 include:_spf57650.spf-protect.dk -all
  • _globalsign-domain-verification=0NziJ4PJI6FztRjH_G73g_YpNbctrf3RhPJ9WPRZ0l
  • _globalsign-domain-verification=V25hLqNHiUIavjdMxUdOiR-4q4CboHYTfnmLlg6Hhh
  • atlassian-domain-verification=10JdWVmKVI62KtF5CRGK8EcVThvoJb8nADn8p8GpIaqzG0oPfjzmspH5llpr9prI

NS 4

  • ns1-06.azure-dns.com
  • ns2-06.azure-dns.net
  • ns3-06.azure-dns.org
  • ns4-06.azure-dns.info

SOA 1

  • ns1-06.azure-dns.com azuredns-hostmaster.microsoft.com

MCP_RECORDS 1

  • v=spf1 redirect=urban.partners

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:671a935ec701a@dmarc-dk.centerasecurity.com;

BIMI_RECORDS 1

  • v=spf1 redirect=urban.partners

MTA_STS_RECORDS 1

  • v=spf1 redirect=urban.partners

TLS Certificates (3)

Common NameIssuerExpires
urban.partners C=US, O=Let's Encrypt, CN=YR1 Thu, 29 Oct 2026 21:09:01 +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_c22c6daca087d49f
Output Hash
c8693c58042a4d7c491cf3ebe0a0a516865313c96572dd93a9f92fba5e9b1ce2
Signature
ed25519:0be1ea9d78bd1a65421fd5e559fe763f4c3caaebb9e7668c511c85c46982e3d0b6d85f00c38e02c77ae6660945ec6f70586698c9239f05afddf9130e0b95da08
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser