Domain report
Everything about a domain on one page: where it is registered and hosted, whether its email is protected against spoofing, its DNS, and how secure its website is. Every problem comes with why it matters and how to fix it.
Report for company.com
Problem: company.com: mostly healthy, 1 thing to fix
Grade B · 80 out of 100
Every check that finished counts: 100 points, minus 20 for each problem and 8 for each warning. A from 90 points, B from 80, C from 65, D from 50, otherwise F.
- −20 Security headers: Security headers: grade F (25/100).
Key facts
| Domain | company.com · Grade B · 80 out of 100 |
|---|---|
| Registrar and expiry | OK: GoDaddy.com, LLC · Expires on 2035-05-27, in 3108 days. |
| Hosting | OK: 104.21.75.54 · Cloud or hosting provider 172.67.214.210 · Cloud or hosting provider 2606:4700:3031::6815:4b36 · Cloud or hosting provider 2606:4700:3034::ac43:d6d2 · Cloud or hosting provider |
| Mail servers | Note: No MX records: this domain does not receive email. |
| SPF | Note: No SPF record: nothing says which servers may send email for this domain. |
| DKIM | Note: No DKIM key found among the common selectors (google, selector1, selector2, default, k1, s1, mail). The domain may still use DKIM with a different selector. |
| DMARC | OK: DMARC is p=reject: failing email is rejected. |
| TLS certificate | OK: Latest certificate from Google Trust Services (WE1), valid until 2026-12-15 (23 days). |
| Website | OK: The website answers with HTTP 200 at https://company.com/. HTTP 200 |
| Security headers | Problem: Security headers: grade F (25/100). What this means |
| Name servers / DNS provider | OK: daisy.ns.cloudflare.com, mustafa.ns.cloudflare.com · Cloudflare |
Signals
- Problem: Weak security headers
- OK: Domain not expiring soon
- OK: DMARC enforced
- OK: Website up
- OK: Valid certificate
- OK: No abuse found in our lists
Scores from other services (we don't copy them)
We check registration, DNS, email authentication, the website, its certificate and our own lists. We don't scan for malware or query mail blocklists (DNSBLs), and we can't test the mail servers themselves (port 25): use the links for those.
Passed 10 · Warnings 0 · Problems 1 · Notes 8
Domain
OK
| Registration | OK: Registered with GoDaddy.com, LLC. |
|---|---|
| Expiry | OK: Expires on 2035-05-27, in 3108 days. |
| Status | OK: No hold or deletion status. |
| Registrar | GoDaddy.com, LLC |
| Registered | 1994-07-08 |
| Expires | 2035-05-27 |
| Age | 32 years |
| Status | client delete prohibited client renew prohibited client transfer prohibited client update prohibited |
Website
OK
| Website | OK: The website answers with HTTP 200 at https://company.com/. |
|---|---|
| HTTPS redirect | OK: http:// redirects to https://. |
| Final address | https://company.com/ |
| HTTP status | 200 |
Certificate
OK
| Certificate | OK: Latest certificate from Google Trust Services (WE1), valid until 2026-12-15 (23 days). |
|---|---|
| Issuer | Google Trust Services (WE1) |
| Valid until | 2026-12-15 |
| Certificate record |
Security headers
Problem
| Security headers | Problem: Security headers: grade F (25/100). |
|---|---|
strict-transport-security | Warning: Missing · Forces browsers to use HTTPS on later visits. |
content-security-policy | Set · Limits where scripts and other content may load from, which blocks most injection attacks. |
x-content-type-options | Warning: Missing · Stops browsers from guessing file types (MIME sniffing). |
x-frame-options | Warning: Missing · Stops other sites from embedding this one in a frame (clickjacking). |
referrer-policy | Warning: Missing · Controls how much of the page address is sent to other sites. |
permissions-policy | Warning: Missing · Turns off browser features the site does not need, such as the camera. |
Email security
OK
| Mail servers | Note: No MX records: this domain does not receive email. |
|---|---|
| SPF | Note: No SPF record: nothing says which servers may send email for this domain. |
| DMARC | OK: DMARC is p=reject: failing email is rejected. |
| DKIM | Note: No DKIM key found among the common selectors (google, selector1, selector2, default, k1, s1, mail). The domain may still use DKIM with a different selector. |
| MTA-STS | Note: No MTA-STS policy. |
| BIMI | Note: No BIMI record. |
| TLS-RPT | Note: No TLS-RPT record: you won't hear about failed encrypted deliveries. Optional. |
DMARC record ?DMARC is a DNS TXT record at _dmarc.<domain>. It tells receivers what to do with email that fails SPF and DKIM: nothing, spam folder, or reject. | v=DMARC1; p=reject; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net; |
| DKIM selectors checked | google, selector1, selector2, default, k1, s1, mail |
DNS
OK
| Name servers | OK: 2 name servers. |
|---|---|
| CAA | Note: No CAA record: any certificate authority may issue certificates. |
| DNSSEC | Note: DNSSEC is off. |
| Name servers | daisy.ns.cloudflare.com mustafa.ns.cloudflare.com |
| SOA | daisy.ns.cloudflare.com. dns.cloudflare.com. 2420134271 10000 2400 604800 1800 |
DNSSEC ?DNSSEC signs DNS answers so resolvers can check they were not tampered with. Validating resolvers mark checked answers with the AD (authenticated data) flag. | None |
Hosting
OK
| Address | OK: Points to 104.21.75.54. |
|---|---|
| IPv6 | OK: Reachable over IPv6 as well. |
| IPv4 addresses | 104.21.75.54 172.67.214.210 |
| IPv6 addresses | 2606:4700:3031::6815:4b36 2606:4700:3034::ac43:d6d2 |
Network (ASN) ?An ASN (Autonomous System Number) identifies one network on the internet, usually an internet provider, a hosting company or a large organization. All of its IP addresses are announced under this number. | AS13335 Cloudflare, Inc. |
| 104.21.75.54 | Cloud or hosting provider · This address belongs to Cloudflare. |
| 172.67.214.210 | Cloud or hosting provider · This address belongs to Cloudflare. |
| 2606:4700:3031::6815:4b36 | Cloud or hosting provider · This address belongs to Cloudflare. |
| 2606:4700:3034::ac43:d6d2 | Cloud or hosting provider · This address belongs to Cloudflare. |
DNS records
| A The IPv4 address a name points to. | 104.21.75.54 172.67.214.210 |
|---|---|
| AAAA The IPv6 address a name points to. | 2606:4700:3031::6815:4b36 2606:4700:3034::ac43:d6d2 |
| MX The mail servers that receive email for the domain, with a priority number (lower is tried first). | None |
| NS The name servers that are authoritative for the domain, which usually tells you the DNS provider. | daisy.ns.cloudflare.com mustafa.ns.cloudflare.com |
| TXT Free-form text. Used for email security (SPF, DMARC, DKIM) and to prove domain ownership to services. | None |
| TXT _dmarc.company.com Free-form text. Used for email security (SPF, DMARC, DKIM) and to prove domain ownership to services. | v=DMARC1; p=reject; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net; |
| SOA Zone metadata: the primary name server, an admin contact and a serial number. | daisy.ns.cloudflare.com. dns.cloudflare.com. 2420134271 10000 2400 604800 1800 |
| CAA Which certificate authorities may issue TLS certificates for the domain. | None |
Fix it: suggested records
These records are suggestions built from what this report found. Review each one before you publish it: a wrong record can stop email or certificates from working.
SPF record New record
| Name | company.com |
|---|---|
| Type | TXT |
| Value | v=spf1 -all |
For a domain that never sends email: no server may send mail as company.com. Don't use it if anything sends mail from this domain.
company.com. 3600 IN TXT "v=spf1 -all"
CAA record New record
| Name | company.com |
|---|---|
| Type | CAA |
| Value | 0 issue "pki.goog" |
Only pki.goog would be allowed to issue certificates for company.com, based on your current certificate. If anything else issues certificates for you (another provider, your CDN), add a line for it too, or renewals will fail.
company.com. 3600 IN CAA 0 issue "pki.goog"
Check it elsewhere
These services have their own data and terms. We only link to them: the address is sent to them only if you click.
What this means and where the data comes from
What the findings mean
Problem: Security headers
Why this matters. Security headers tell browsers to block common attacks such as clickjacking and content injection.
How to fix. Add the missing headers listed above in your web server or CDN configuration.
Where the data comes from
- Source: RDAP (rdap.org)
- Source: a request from iplover to https://company.com/ (at most 5 redirects, 8 seconds)
- Source: crt.sh Certificate Transparency logs. This is the newest certificate logged for the domain, not necessarily the one the server shows right now.
- Source: DNS over HTTPS (Cloudflare, with Google Public DNS as fallback)
- Reputation: iplover's own copies of public blocklists and network lists, refreshed every hour. See every list and its date.
Checked 2026-11-22 04:10 UTC. Reports are cached for up to 1 hour.
Notes and limitations
We check registration, DNS, email authentication, the website, its certificate and our own lists. We don't scan for malware or query mail blocklists (DNSBLs), and we can't test the mail servers themselves (port 25): use the links for those.
Report for company.com
Checked 2026-11-22 04:10 UTC. Reports are cached for up to 1 hour.
02 · Domain
[OK] Registered with GoDaddy.com, LLC.
[OK] Expires on 2035-05-27, in 3108 days.
[OK] No hold or deletion status.
03 · Hosting
[OK] Points to 104.21.75.54.
[OK] Reachable over IPv6 as well.
04 · Email security
[Note] No MX records: this domain does not receive email.
[Note] No SPF record: nothing says which servers may send email for this domain.
[OK] DMARC is p=reject: failing email is rejected.
[Note] No DKIM key found among the common selectors (google, selector1, selector2, default, k1, s1, mail). The domain may still use DKIM with a different selector.
[Note] No MTA-STS policy.
[Note] No BIMI record.
[Note] No TLS-RPT record: you won't hear about failed encrypted deliveries. Optional.
05 · DNS
[OK] 2 name servers.
[Note] No CAA record: any certificate authority may issue certificates.
[Note] DNSSEC is off.
06 · Website
[OK] The website answers with HTTP 200 at https://company.com/.
[OK] http:// redirects to https://.
[Problem] Security headers: grade F (25/100).
How to fix: Add the missing headers listed above in your web server or CDN configuration.
07 · Certificate
[OK] Latest certificate from Google Trust Services (WE1), valid until 2026-12-15 (23 days).
https://iplover.com/report?domain=company.com
What this tool does
The domain report checks a domain from our server in one go, using public sources only: the registry's RDAP record for the registrar and the creation and expiry dates, DNS over HTTPS for the name servers and records, Certificate Transparency logs (crt.sh) for the TLS certificate, and one ordinary HTTPS request to the website for its redirects and security headers.
Email protection is read from DNS: the MX records, SPF (including how many DNS lookups it needs), DMARC, DKIM on common selectors, MTA-STS, TLS-RPT and BIMI. Every finding has a status, why it matters and, where the owner can fix something, the record or setting to change.
We don't log in to anything, scan ports or send email. Results are kept in a short cache only, so repeated checks don't hit the same servers again.
How to read the results
- The grade (A to F) sums up the checks the domain's owner can fix. A check we couldn't complete is marked “Couldn't check” and never lowers the grade.
- Key facts come first: registrar and expiry, hosting and server location, name servers, email protection and the certificate. Rows with a problem are highlighted and say why.
- DKIM can only be checked on the selectors we try (google, selector1, selector2, default, k1, s1, mail). “Not found” means not under those names, not that the domain has no DKIM.
- Server location is where the address is registered or its network is based: an estimate, not a street address. Behind a CDN it is the CDN's location.
- Fix it shows the exact DNS record or setting for each problem. Check it against your DNS provider's instructions before you publish it.
Frequently asked questions
Why does it say DKIM was not found when my email works?
A DKIM key lives under a selector name that only the sender chooses. We try the common ones; if yours uses another, find the s= value in the DKIM-Signature header of an email you sent and look up that name with the DNS lookup tool.
Why do some rows say “Couldn't check”?
A source didn't answer in time: the registry, crt.sh, a DNS query or the website itself. Those checks don't count against the grade. An incomplete report is kept only for a few minutes, so trying again later can complete it.
Can I check a subdomain?
Yes. The DNS, website and certificate checks use the exact name you enter; the registration details come from the registered domain above it.
Does the domain owner see that I checked?
Not as you: the check comes from our server, not your browser. We read public DNS and registry records and make one ordinary HTTPS request to the website, like any visitor opening the homepage.