Skip to content
https://1nom.org

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.21.15.90: lookup 104.21.15.90: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 172.67.205.169: lookup 172.67.205.169: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3035::6815:f5a: lookup 2606:4700:3035::6815:f5a: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3034::ac43:cda9: lookup 2606:4700:3034::ac43:cda9: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 23 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 23 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.1nom.org/
https://1nom.org/

HTTP → HTTPS

http://www.1nom.org/

HTTP version does not redirect to HTTPS

B
TLS Certificate Expiry & Recommendations
72 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

72
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A
DNS Records
2 A records, 43 ms lookup
PASS
2 A records, 43 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.15.90, 172.67.205.169
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3035::6815:f5a, 2606:4700:3034::ac43:cda9
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 43 ms
Got: 43 ms
A104.21.15.90, 172.67.205.169
AAAA2606:4700:3035::6815:f5a, 2606:4700:3034::ac43:cda9
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 43 ms

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 18ms across 3 resolvers (spread 21ms)
PASS
Mean 18ms across 3 resolvers (spread 21ms)
Info::
Quad9: 8ms
Got: 8ms via 9.9.9.9:53
Info::
Cloudflare: 18ms
Got: 18ms via 1.1.1.1:53
Info::
Google: 29ms
Got: 29ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.1nom.org

https://www.1nom.org

319 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.1nom.org200319 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3035::6815:f5a, 2606:4700:3034::ac43:cda9
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3035::6815:f5a, 2606:4700:3034::ac43:cda9 Connection Reachable (17 ms)
A
Domain Intelligence
1nom.org — via Key-Systems GmbH, 8 years, 10 months old
PASS
1nom.org — via Key-Systems GmbH, 8 years, 10 months old
Warning::
Domain expires in 78 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Feb 8, 2027
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Key-Systems GmbH
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

77 days

February 8, 2027

SSL certificate

72 days

Issued by Let's Encrypt

Domain age

8 years, 10 months

Registered February 8, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:8424:5fe8:b901:ae7e:1e4c:32be:143e

Registrar

Key-Systems GmbH

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Key-Systems GmbH
Created February 8, 2018 (8 years, 10 months ago)
Expires February 8, 2027 (2 months)
Last Updated November 4, 2026
Name Servers boyd.ns.cloudflare.com, hadlee.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2a02:8424:5fe8:b901:ae7e:1e4c:32be:143e
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 427 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
28 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
417 ms
Total Time Total request time from DNS lookup through full response.
428 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 17 ms TLS Handshake 28 ms Server Processing 337 ms Content Transfer 11 ms
A
CDN & Delivery
Document on Cloudflare; assets also on Akamai
PASS
Document on Cloudflare; assets also on Akamai
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a5e0a3b109bc0261-CDG
Info::
CDN cache status: DYNAMIC
Info::
Assets on Akamai: analytics.tiktok.com (assets: 3), cache TCP_MEM_HIT from a95-100-85-205.deploy.akamaitechnologies.com (AkamaiGHost/22.7.1-a99db5fb656d033f98675045e2711319) (-)
Got: x-akamai-request-id: 4c08ad67
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a5e0a3b109bc0261-CDG

Asset hosts on a CDN

  • analytics.tiktok.com — Akamai · assets: 3 · Cache Status: TCP_MEM_HIT from a95-100-85-205.deploy.akamaitechnologies.com (AkamaiGHost/22.7.1-a99db5fb656d033f98675045e2711319) (-)

Other asset hosts

  • fonts.googleapis.com — assets: 6 · Google
  • fundingchoicesmessages.google.com — assets: 3 · Google
  • pagead2.googlesyndication.com — assets: 3 · Google
  • www.googletagmanager.com — assets: 1 · below probe threshold
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
A+
Health Check Endpoint
Health endpoint at https://www.1nom.org/healthz (HTTP 200)
PASS
Health endpoint at https://www.1nom.org/healthz (HTTP 200)
Info::
Public health endpoint at https://www.1nom.org/healthz
Got: https://www.1nom.org/healthz
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback