Skip to content
https://www.osintatlas.io

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 8 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 172.66.46.227: lookup 172.66.46.227: 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.66.45.29: lookup 172.66.45.29: 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:310c::ac42:2ee3: lookup 2606:4700:310c::ac42:2ee3: 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:310c::ac42:2d1d: lookup 2606:4700:310c::ac42:2d1d: 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
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
CDN & Delivery
Cloudflare Pages
REVIEW
Cloudflare Pages
Info::
Document is served via Cloudflare Pages CDN
Got: delegation osint-atlas.pages.dev
Document served via CDN: Cloudflare Pages
Provider Cloudflare Pages Evidence delegation osint-atlas.pages.dev
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
2 A records, 37 ms lookup
PASS
2 A records, 37 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.46.227, 172.66.45.29
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:310c::ac42:2ee3, 2606:4700:310c::ac42:2d1d
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: osint-atlas.pages.dev
Info::
2 nameserver(s) configured
Got: gigi.ns.cloudflare.com, vin.ns.cloudflare.com
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: 37 ms
Got: 37 ms
A172.66.46.227, 172.66.45.29
AAAA2606:4700:310c::ac42:2ee3, 2606:4700:310c::ac42:2d1d
CNAMEosint-atlas.pages.dev
NSgigi.ns.cloudflare.com, vin.ns.cloudflare.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 37 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 26ms across 3 resolvers (spread 12ms)
PASS
Mean 26ms across 3 resolvers (spread 12ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 26ms
Got: 26ms via 1.1.1.1:53
Info::
Quad9: 32ms
Got: 32ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.osintatlas.io

https://www.osintatlas.io

190 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.osintatlas.io200190 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:310c::ac42:2ee3, 2606:4700:310c::ac42:2d1d
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:310c::ac42:2ee3, 2606:4700:310c::ac42:2d1d Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 422 URLs
PASS
robots.txt present, sitemap with 422 URLs
Info::
robots.txt is present
Got: 92 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 422 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 92 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /data/
Sitemap: https://osintatlas.netlify.app/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 422 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.osintatlas.io/
301https://osintatlas.io/

Preferred variant: www

HTTP → HTTPS

301http://www.osintatlas.io/ → https://www.osintatlas.io/

Consistent

A+
Domain Intelligence
osintatlas.io — via Name.com, Inc., 14 days old, hosted on AWS
PASS
osintatlas.io — via Name.com, Inc., 14 days old, hosted on AWS
Info::
Domain registered until Oct 20, 2027 (11 months remaining)
Info::
Domain is only 14 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Oct 20, 2026
Info::
Registrar: Name.com, Inc.
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

346 days

October 20, 2027

SSL certificate

75 days

Issued by Google Trust Services

Domain age

14 days

Registered October 20, 2026

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

35.157.26.135

Registrar

Name.com, Inc.

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
Registrar Name.com, Inc.
Created October 20, 2026 (14 days ago)
Expires October 20, 2027 (11 months)
Last Updated October 25, 2026
Name Servers dns4.p03.nsone.net, dns3.p03.nsone.net, dns2.p03.nsone.net, dns1.p03.nsone.net
Registrant Domain Protection Services, Inc.
Hosting
IP Address 35.157.26.135
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (2.4s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 63 ms TCP Connect 19 ms TLS Handshake 26 ms Server Processing 336 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback