bitly.su

Observed Aug 16, 2026, 13:43 UTC (3h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Not responding
Runs onOVH SAS
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-16 13:43 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 bitly.su actually stands on - every host below is a signed observation
bitly.su
A / AAAA
37.187.83.72176.31.179.191
OVH SASserves the site
NS
dns1.ru-tld.rudns2.ru-tld.ru
ru-tld.ruanswers its DNS

DNS Records

A 2

  • 37.187.83.72
  • 176.31.179.191

TXT 3

  • v=spf1 ip4:127.0.0.1 -all
  • eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJEb21haW5TaG9wIiwic3ViIjoiNTU1NDQ0L05JQy1EIn0.U0Kf2K3GIXkdshwl_K0NHnXeibFayl8r9Hdz4AalF2g
  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;

NS 2

  • dns1.ru-tld.ru
  • dns2.ru-tld.ru

SOA 1

  • dns.ru-tld.ru support.ru-tld.ru

MCP_RECORDS 3

  • v=spf1 ip4:127.0.0.1 -all
  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;
  • eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJEb21haW5TaG9wIiwic3ViIjoiNTU1NDQ0L05JQy1EIn0.U0Kf2K3GIXkdshwl_K0NHnXeibFayl8r9Hdz4AalF2g

DMARC_RECORDS 3

  • eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJEb21haW5TaG9wIiwic3ViIjoiNTU1NDQ0L05JQy1EIn0.U0Kf2K3GIXkdshwl_K0NHnXeibFayl8r9Hdz4AalF2g
  • v=spf1 ip4:127.0.0.1 -all
  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;

BIMI_RECORDS 3

  • eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJEb21haW5TaG9wIiwic3ViIjoiNTU1NDQ0L05JQy1EIn0.U0Kf2K3GIXkdshwl_K0NHnXeibFayl8r9Hdz4AalF2g
  • v=spf1 ip4:127.0.0.1 -all
  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;

MTA_STS_RECORDS 3

  • eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJEb21haW5TaG9wIiwic3ViIjoiNTU1NDQ0L05JQy1EIn0.U0Kf2K3GIXkdshwl_K0NHnXeibFayl8r9Hdz4AalF2g
  • v=spf1 ip4:127.0.0.1 -all
  • v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;

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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_88b5985190307dd2
Output Hash
e02422dc2e55de4383adb7e310307ffb969ac92b0138608c0fb8bc310d66d33c
Signature
ed25519:3f17027c2c9ee7de89864caadea248eb0e3436f42d21cfe2261bc3e936af2658530fd9931c30b41f506d2a3c3e8a3ed65f2b658cc7e11315f381866049925609
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT41,087 material changesacross 39,123 domains · 24h to ~80m ago · -472 vs yesterdayROTATION63 domains moved DNS from magpiedns.com to koaladns.com, 61 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email provider24hNOW589 curated domains not reachable+94 vs yesterdaySITE ERRORS36,075 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,370 sites429 rate-limit / 403 bot-block, a posture signal