ramtha.com
Observed Aug 16, 2026, 08:25 UTC (20h 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.
GlobalSign
Google Search ConsoleSteady. No change on record for ramtha.com in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.
DNS Records
A 4
151.101.67.52151.101.195.52151.101.3.52151.101.131.52
MX 1
0mail.ramtha.com
TXT 3
_globalsign-domain-verification=F73WYuxssbwI8HY4DCOhz2ru8fhhyH6gprOslu4Rw6v=spf1 mx:ramtha.com a:ramtha.com ~allgoogle-site-verification=5zcx0IWdvwXScTBhQtWrXla1du6Bzkmfa07FhQ2HM8I
NS 2
ns1.liquidweb.comns.liquidweb.com
SOA 1
ns.liquidweb.com admin.liquidweb.com
MCP_RECORDS 3
v=spf1 mx:ramtha.com a:ramtha.com ~all_globalsign-domain-verification=F73WYuxssbwI8HY4DCOhz2ru8fhhyH6gprOslu4Rw6google-site-verification=5zcx0IWdvwXScTBhQtWrXla1du6Bzkmfa07FhQ2HM8I
DMARC_RECORDS 1
v=DMARC1; p=none; rua=mailto:e2a2d85b@mxtoolbox.dmarc-report.com, mailto:webmaster@ramtha.com; ruf=mailto:e2a2d85b@forensics.dmarc-report.com, mailto:webmaster@ramtha.com; fo=1
BIMI_RECORDS 3
google-site-verification=5zcx0IWdvwXScTBhQtWrXla1du6Bzkmfa07FhQ2HM8I_globalsign-domain-verification=F73WYuxssbwI8HY4DCOhz2ru8fhhyH6gprOslu4Rw6v=spf1 mx:ramtha.com a:ramtha.com ~all
MTA_STS_RECORDS 3
_globalsign-domain-verification=F73WYuxssbwI8HY4DCOhz2ru8fhhyH6gprOslu4Rw6v=spf1 mx:ramtha.com a:ramtha.com ~allgoogle-site-verification=5zcx0IWdvwXScTBhQtWrXla1du6Bzkmfa07FhQ2HM8I
TLS Certificates (2)
| Common Name | Issuer | Expires |
|---|---|---|
ramtha.com |
C=US, O=Certainly, CN=Certainly Intermediate R1 | Thu, 27 Aug 2026 20:32:48 +0000 |
Certainly Intermediate R1 |
C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Root Certificate Authority - G2 | Mon, 21 Jun 2032 23:59:59 +0000 |
Subdomains (1)
DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works
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 receiptEd25519 Receipt
- Receipt ID
rcpt_7239300874f97cb4- Output Hash
d83dbe7498d0d3ef72f476e6c4760852a7df2cb8c367cfcd77c2282954be8edf- Signature
ed25519:65d329b7908abd51a58447d7e187a2f58038fc20719191a5df2fc41492908afdc439c22ae1570ceaae89f6fb9748c1fbd8a70ac36f5e66ab3e3814fc9273440a- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast