CONTINUOUS INTERNET TELEMETRY24H DRIFT3,075 material changesacross 2,826 domains · -323 vs yesterdayDNS DRIFT17 domains changed DNS providertop destination cloudflare.com · -10 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.com · -1 vs yesterdayCERT DRIFT5 domains switched issuing CA24h · -2 vs yesterdayNOW3,324 curated domains not answering-6,394 vs yesterdayERRORS10,910 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,075 material changesacross 2,826 domains · -323 vs yesterdayDNS DRIFT17 domains changed DNS providertop destination cloudflare.com · -10 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.com · -1 vs yesterdayCERT DRIFT5 domains switched issuing CA24h · -2 vs yesterdayNOW3,324 curated domains not answering-6,394 vs yesterdayERRORS10,910 responded with an errorlast probe · 5xx / 404 / 429 / 403

buffalo.jp

Observed 2026-07-13T03:22:52.100Z (17h ago). Every field below was attested with an Ed25519 signature at scan time.

Not responding
Runs onAmazon
Email byMicrosoft 365
Also usesGoogle Search Console
15 subdomains · tranco_20k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat buffalo.jp actually stands on - every host below is a signed observation
buffalo.jp
A / AAAA
52.194.172.187
Amazonserves the site
NS
ns-906.awsdns-49.netns-311.awsdns-38.comns-1957.awsdns-52.co.ukns-1293.awsdns-33.org
awsdns-49.net + awsdns-38.com + moreanswers its DNS
MX
buffalo-jp.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

timeout No response within the timeout Connection timed out - no response within 3s
HTTP status0
Servernot observed
TLS protocolnot observed
TLS issuernot observed
Behind Cloudflareno
Response time6200 ms
DNS resolutionNOERROR

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

DNS Records

A 1

  • 52.194.172.187

MX 1

  • 0buffalo-jp.mail.protection.outlook.com

TXT 6

  • google-site-verification=mGYZCOzc8g7aO_FYu9sA032b13GVv_bPdrJzKQYh024
  • google-site-verification=aSIm0_d8ullI1QcLjzPu9M7ofVJbIWGZjEf_BsDYLi8
  • v=spf1 include:spf.protection.outlook.com ip4:153.153.140.130 a:smtp2.buffalo.ne.jp ip4:54.150.187.103 -all
  • MS=ms27150604
  • google-site-verification=3TradF7z9Gs5raOxOtJS-cvZa-j0Y7EGp5UKbNuUPbU
  • v=DMARC1; p=none;

NS 4

  • ns-906.awsdns-49.net
  • ns-311.awsdns-38.com
  • ns-1957.awsdns-52.co.uk
  • ns-1293.awsdns-33.org

SOA 1

  • ns-1293.awsdns-33.org awsdns-hostmaster.amazon.com

TLS Certificates (0)

None.

Subdomains (15)

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

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

Ed25519 Receipt

Receipt ID
c498ae76-b38d-4bce-8937-9c232a08b3f6
Output Hash
75e18451383fcc2d609fb0fb73043bd7221e1a2e7c34430c7e12977d80c8d4f4
Signature
ed25519:21dc4edc98068c53d94142ca0c737f70147e954a0524dab075c0376af0f5ff84fd8dcef2f3c478bad9db2c317e95a84e4a6491a1932cfaa5d3e41afbf5014a00
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser