CONTINUOUS INTERNET TELEMETRY24H DRIFT3,043 material changesacross 2,698 domains · -355 vs yesterdayDNS DRIFT25 domains changed DNS providertop destination cloudflare.com · -2 vs yesterdayEMAIL DRIFT3 domains switched email providertop destination h-email.net · -3 vs yesterdayCERT DRIFT7 domains switched issuing CA24hNOW3,308 curated domains not answering-6,410 vs yesterdayERRORS10,957 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,043 material changesacross 2,698 domains · -355 vs yesterdayDNS DRIFT25 domains changed DNS providertop destination cloudflare.com · -2 vs yesterdayEMAIL DRIFT3 domains switched email providertop destination h-email.net · -3 vs yesterdayCERT DRIFT7 domains switched issuing CA24hNOW3,308 curated domains not answering-6,410 vs yesterdayERRORS10,957 responded with an errorlast probe · 5xx / 404 / 429 / 403

omeda.com

Observed 2026-07-13T07:55:27.151Z (4h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Registered withDynadot Inc
Also usesGoogle Search ConsoleAtlassianStripeFacebook/Meta
16 subdomains · tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat omeda.com actually stands on - every host below is a signed observation
omeda.com
A / AAAA
204.180.130.40
Cloudflareserves the site
NS
b1.uberns.orga1.uberns.neta1.uberns.co.uka1.uberns.com+1 more
uberns.org + uberns.net + moreanswers its DNS
MX
omeda-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

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

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

DNS Records

A 1

  • 204.180.130.40

MX 1

  • 15omeda-com.mail.protection.outlook.com

TXT 18

  • google-site-verification=jgtt-8MA2nJQ7tPThqefwUUkRtMX2ME6oXQfUqwNooU
  • atlassian-domain-verification=u25Fs/E7rtABDso4m7ck33fqRGFxlmIRJNQBCfHE/uaqPLwWlLcmm2YjCxTRBfVa
  • stripe-verification=9FFDBCBF0CD4619E4C081C5542DFA6409F754FC3AABEB5FA8DCE453CF3EF2B5C
  • MS=ms31747739
  • atlassian-sending-domain-verification=5543f250-4f0a-412f-8ceb-e50e612175c4
  • apple-domain-verification=xMn-rGhbgfIsXi2eHgmYmb_wXJLX3OQD9gn0eKTbapc
  • google-site-verification=OoCI7mmLRP3_1_jU6C4lovMXlBaXEFWUNoz0nX81fy4
  • status-page-domain-verification=phzpf8t9d79w
  • nordpass-domain-verification=676a82be5ff983c860cfd9320c7101c1bef7f61b2b5959578154bb810b74679d
  • atlassian-sending-domain-verification=84cbdc87-3b4e-41ba-bf7a-3e2b01c3aa8a

NS 5

  • b1.uberns.org
  • a1.uberns.net
  • a1.uberns.co.uk
  • a1.uberns.com
  • b1.uberns.info

SOA 1

  • a1.uberns.com hostmaster.omeda.com

TLS Certificates (0)

None.

Subdomains (16)

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 omeda.com. It updates itself. It attests a signed observation - not that the site is safe.

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

Ed25519 Receipt

Receipt ID
119bc90d-f378-4f20-a1ff-071d381494d4
Output Hash
6bf4f9fe629051b1ebd51359122a37ac0ebc0935cc67988b697265483689fc69
Signature
ed25519:418159a7b6812f4c8752cda0d1e5191da8a140f97dc191ba655245d2c5f7fdda905a14b6b4bc0a30c56a8d40aa17e9dbc8a25c614969a21e56b07624263de001
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser