CONTINUOUS INTERNET TELEMETRY24H DRIFT1,810 material changesacross 1,618 domains · +388 vs yesterdayDNS DRIFT2 domains changed DNS providertop destination yandexcloud.net · -19 vs yesterdayEMAIL DRIFT1 domain switched email providertop destination google.com · -4 vs yesterdayNOW1,106 curated domains not answering+396 vs yesterdayERRORS4,988 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED7,738 throttled or blocked our scanner429 rate-limit / 403 bot-blockMOVERtiktok.comDMARC enforcement downgraded: p=reject → no DMARC record24H DRIFT1,810 material changesacross 1,618 domains · +388 vs yesterdayDNS DRIFT2 domains changed DNS providertop destination yandexcloud.net · -19 vs yesterdayEMAIL DRIFT1 domain switched email providertop destination google.com · -4 vs yesterdayNOW1,106 curated domains not answering+396 vs yesterdayERRORS4,988 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED7,738 throttled or blocked our scanner429 rate-limit / 403 bot-blockMOVERtiktok.comDMARC enforcement downgraded: p=reject → no DMARC record

foetex.dk

Observed 2026-07-18T01:11:57.683Z (8h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Also usesFacebook/MetaGoogle Search ConsoleAtlassian
5 subdomains · push_legacy
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat foetex.dk actually stands on - every host below is a signed observation
foetex.dk
A / AAAA
75.2.60.5
Cloudflareserves the site
NS
ns.dandomain.dkns2.dandomain.dk
dandomain.dkanswers its DNS
MX
foetex-dk.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.foetex.dk/
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time143 ms
DNS resolutionNOERROR
Redirect chain
https://www.foetex.dk/

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

DNS Records

A 1

  • 75.2.60.5

MX 1

  • 0foetex-dk.mail.protection.outlook.com

TXT 10

  • facebook-domain-verification=twxzrpis1t2a1hylqoufkuw0mp74st
  • hibp-verify=dweb_en60qx8uldfbzrcglbkga6k5
  • MS=ms31010454
  • google-site-verification=vd53qaqEy4Dxn44aek8pMsihCzzXrkQSlLzA6_aGLuU
  • v=spf1 include:spf.dsg.dk include:mktomail.com include:spf.mandrillapp.com ip4:72.32.148.89/32 ip4:24.155.144.8/32 -all
  • amazonses:peLXiMcotqO+IWNVX3tVgkxHoRHs1cynbVNmgcmXCUs=
  • google-site-verification=tOd2X5ycXrMr7FIfYhpzg4iJgphnlJQS11O6OCUVI0c
  • atlassian-domain-verification=lmVyu+XazqJjuaZ5NabP99nBC+XiZmMkwg0UAK0e4FxgHK10Rp694Amfqq3cyWyr
  • v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:dmarc_agg@vali.email
  • v=DNSSEC1; (detected)

NS 2

  • ns.dandomain.dk
  • ns2.dandomain.dk

SOA 1

  • ns.dandomain.dk hostmaster.dandomain.dk

TLS Certificates (0)

None.

Subdomains (5)

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

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for foetex.dk. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for foetex.dk <a href="https://domaindrift.io/t/foetex.dk"> <img src="https://domaindrift.io/badge/foetex.dk.svg" width="300" height="64" alt="DomainDrift signed observations for foetex.dk"> </a>

Ed25519 Receipt

Receipt ID
385defc4-f1e7-4020-8acd-88c4de3f81e1
Output Hash
5ab028a5839abf37d20d56b9d0ece8f9cd4e8374a9ead60b9922ad309df9ab9c
Signature
ed25519:d4c83fae9913e9aa98f2d5e505e844eebf4ae0c42d731b69fb6fa5f9b52999f0b5dda4ec836323a0f02788d107e87c22cf62284531be5ad4f06485cdb34b5e01
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
Verify this in your browser