Opens the print dialog of your browser. Choose "Save as PDF" as the printer there to get a file: the browser writes it, nothing is uploaded.
Share a snapshot of this report
A live report changes with every lookup, so a shared link to it would not show what you see now. A snapshot stores this report as our server observed it and gives it its own link for 30 days. It holds public lookup data only. Anyone with the link can open it; search engines are asked not to index it.
A domain is not one thing. It is a registration held at a registry, a set of DNS records served by nameservers, one or more servers that answer on the IP addresses those records point to, and usually a mail setup that lives somewhere else entirely. Problems tend to appear in the gaps between those layers, so the report looks at all of them in a single pass.
The registration section comes from RDAP, the structured successor to WHOIS: registrar, creation, update and expiry dates, status codes, nameservers and DNSSEC state. The DNS section queries public recursive resolvers for A, AAAA, NS, MX, TXT, CAA and SOA records. The mail section reads MX, SPF and DMARC. The hosting section maps each IP address to its network owner. The web section makes one HTTPS request and records redirects, the response status and the certificate the server presented.
DKIM keys are published under a selector chosen by the sender, so they cannot be discovered from the domain alone. Find the selector in the s= tag of a DKIM-Signature header.
Findings
No MX records
No MX records were found. Senders may fall back to the A/AAAA address, but the domain does not advertise a mail server.
No SPF record
No TXT record starting with "v=spf1" was found. For a domain that sends no mail, publishing "v=spf1 -all" states that explicitly.
DMARC policy is reject
An enforcing DMARC policy is published (inherited from cloudflare.com). Its pct, alignment and reporting tags were not evaluated.
LiveSource: DNS · public resolvers 1.1.1.1, 8.8.8.8Observed:
Hosting and IP
Cloudflare (AS13335) · edge network, origin not visible
LiveSource: Direct HTTPS request (headers + first 64 KB of HTML)Observed:
Change history
What this service recorded for this name on earlier checks. A check happens only when someone opens a report or calls the API: nothing is scheduled, so gaps between checks are normal.
4 checks since Oct 11, 2026, the latest on Oct 11, 2026.
Changes observed
No change in the recorded values across 4 checks.
Values on record
Registrar
Cloudflare, Inc. (IANA 1910)
unchanged since Oct 11, 2026, seen in 1 check · Source: RDAP · rdap.verisign.com + rdap.cloudflare.com · Observed:
Expiry date
2033-02-17
unchanged since Oct 11, 2026, seen in 1 check · Source: RDAP · rdap.verisign.com + rdap.cloudflare.com · Observed:
unchanged since Oct 11, 2026, seen in 1 check · Source: RDAP · rdap.verisign.com + rdap.cloudflare.com · Observed:
IPv4 addresses (A)
104.18.2.142, 104.18.3.142
unchanged since Oct 11, 2026, seen in 3 checks · Source: DNS · public resolvers 1.1.1.1, 8.8.8.8 · Observed:
IPv6 addresses (AAAA)
2606:4700::6812:28e, 2606:4700::6812:38e
unchanged since Oct 11, 2026, seen in 3 checks · Source: DNS · public resolvers 1.1.1.1, 8.8.8.8 · Observed:
Certificate issuer
Google Trust Services · WE1
unchanged since Oct 11, 2026, seen in 1 check · Source: Direct HTTPS request (headers + first 64 KB of HTML) · Observed:
Certificate expiry
2027-01-07
unchanged since Oct 11, 2026, seen in 1 check · Source: Direct HTTPS request (headers + first 64 KB of HTML) · Observed:
The history is kept for the domain name only; nothing about who looked it up is stored. Entries not seen again for 400 days are deleted. Changing A, AAAA and hosting values are normal for sites behind load balancers or content delivery networks.
How this domain compares
Fixed points of reference, not rankings. Each line says what the value is compared with and where it came from.
5 nameservers in the registry record. RFC 1034 asks for at least two; two to four is the usual range, and more is common for large operators.Source: RDAP · rdap.verisign.com + rdap.cloudflare.com · Observed:
DNSSEC: the registry record carries DS data, so resolvers can validate the zone. The DNSSEC checker tests the chain.Source: RDAP · rdap.verisign.com + rdap.cloudflare.com · Observed:
Registrar: Cloudflare Registrar (IANA ID 1910), sells directly to the public, headquartered in United States. Cloudflare RegistrarSource: IANA Registrar IDs registry, read on 2026-09-21
.com is operated by Verisign; open to anyone. Registration data: RDAP (rdap.verisign.com). .comSource: IANA RDAP bootstrap file and root zone database, read on 2026-09-16
2321 days to the expiry date recorded at the registry. A gTLD registration can be renewed up to ten years ahead.Source: RDAP · rdap.verisign.com + rdap.cloudflare.com · Observed:
Reachable over IPv4 (2 addresses) and IPv6 (2).Source: DNS · public resolvers 1.1.1.1, 8.8.8.8 · Observed:
The addresses belong to the Cloudflare edge network: the origin server is not visible in DNS.Source: Team Cymru IP-to-ASN (DNS) · IP RDAP · PTR · Observed:
Announced by 1 network: AS13335. Allocation country: United States (where the address block is registered, not where the server stands).Source: Team Cymru IP-to-ASN (DNS) · IP RDAP · PTR · Observed:
Certificate lifetime 90 days, 87 days remaining. Publicly trusted certificates issued on this date may be valid for at most 200 days (CA/Browser Forum Baseline Requirements).Source: Direct HTTPS request (headers + first 64 KB of HTML) · Observed:
