Skip to content
https://Defacto.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
11
PASS
6
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
17
6 PASS 11 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.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 2.16.245.185 does not match any cert SAN: a2-16-245-185.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2.16.245.169 does not match any cert SAN: a2-16-245-169.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Multi-Resolver DNS Speed
Mean 61ms across 3 resolvers (spread 106ms)
REVIEW
Mean 61ms across 3 resolvers (spread 106ms)
Info::
Cloudflare: 24ms
Got: 24ms via 1.1.1.1:53
Info::
Google: 31ms
Got: 31ms via 8.8.8.8:53
Info::
Quad9: 130ms
Got: 130ms via 9.9.9.9:53
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

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 403 Expected: 301 redirect to HTTPS

www / non-www

403https://www.Defacto.com/
200https://Defacto.com/

HTTP → HTTPS

403http://Defacto.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
Document and assets on Akamai
REVIEW
Document and assets on Akamai
Info::
Document is served via Akamai CDN
Got: 2.16.245.185 in 2.16.0.0/13 (Akamai)
Info::
Assets on Akamai: dfcdn.defacto.com.tr (assets: 26)
Got: delegation dfcdn.defacto.com.tr.akamaized.net
Document served via CDN: Akamai
Provider Akamai Evidence 2.16.245.185 in 2.16.0.0/13 (Akamai)

Asset hosts on a CDN

  • dfcdn.defacto.com.tr — Akamai · assets: 26

Other asset hosts

  • www.defacto.com.tr — assets: 1 · below probe threshold
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.
A+
DNS Records
2 A records, 89 ms lookup
PASS
2 A records, 89 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 2.16.245.185, 2.16.245.169
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: jo.ns.cloudflare.com, amir.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 89 ms
Got: 89 ms
A2.16.245.185, 2.16.245.169
AAAA—
CNAME—
NSjo.ns.cloudflare.com, amir.ns.cloudflare.com
MX
0 aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt2.aspmx.l.google.com
20 alt3.aspmx.l.google.com
30 alt4.aspmx.l.google.com
TXT
globalsign-domain-verification=BdJEginSdQXa7jbWIR-Ox6PaDPmarJXYR70S3DWmM6
globalsign-domain-verification=5HvgPZhvMIGYIHwj7wxervRusoHPEry22ajU_FpRvH
atlassian-domain-verification=nkg2OucGQjmJmXFKi6xmOknS7GptusaJ6UqwMGEefNeH/pQwVx...
apple-domain-verification=EI3uAOOsyU6Dj4rk
hj-ownership=GhVaUG6t82Fp
globalsign-domain-verification=MChiPDJw-uWgePDP0OqUbOYwUIofTDR_4G0Z5gM0lE
google-site-verification=HJ3URzw0K-ZsQvT93f8ohXIkVdfIuEUmBFZpxsUIqyM
globalsign-domain-verification=oxaDBXFq9kPFPTgssAWREFHU2TTAF2hg_H-yeXWJT3
google-site-verification=5bV-Aa4eoKsE9ZynAD1iy3AYdj-PfxChq9LCdDsi7Go
natro-domain-verification=8137cdbcea5c534b3ef90f95bb9c9278
nYykFiFqWAbtxNYY+XXcR6BeY24YXqV4J8OJKZaOzfzHFqIFyEw6o7TyfJnuEmUOek2e9iMHkcjqmPUj...
globalsign-domain-verification=h6j-w_HRO9rOLy8kuBAvbfZBVPxJe28K3s-cOqR7hd
duo_sso_verification=wE2HdV6DDbLjVtCW60NWFNUIg64NHKRgsdMqqNG8XPjleAIZmJxWspwxgcm...
MS=ms68311100
globalsign-domain-verification=hsgV-ZLDJst25U7nTvKqx5Fz74TcfNeTzUUePFirf3
SPF v=spf1 a:mail.defacto.com ip4:31.145.4.200/24 ip4:84.241.173.135/24 include:mail...
google-site-verification=C9t-ZfrHBoKJtQHPsyVOt2N5wrUuonnwJj6y76lwJ9A
facebook-domain-verification=u30ycqz4lzqqx0it27i56zw79vk8se
_globalsign-domain-verification=5iySEk3ksqyVqPUMhfVoBf51t9QBFX9hIyAc2YC-Jx
openai-domain-verification=dv-KypyQ0HbcOcTHXbg8k1e2sFJ
CAALookup not available with standard resolver
Resolved in 89 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
0 redirect(s), 78 ms total
PASS
0 redirect(s), 78 ms total

https://Defacto.com

78 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Defacto.com40378 msHTTP/1.1
A+
Domain Intelligence
Defacto.com — via GoDaddy.com, LLC, 24 years, 10 months old, hosted on Akamai
PASS
Defacto.com — via GoDaddy.com, LLC, 24 years, 10 months old, hosted on Akamai
Info::
Domain registered until Mar 27, 2030 (3 years, 6 months remaining)
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: GoDaddy.com, LLC
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.
Info::
Hosting: Akamai
Got: AS20940
Domain expiry

1256 days

March 27, 2030

SSL certificate

57 days

Issued by Let's Encrypt

Domain age

24 years, 10 months

Registered March 27, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS20940

2.16.245.169

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created March 27, 2002 (24 years, 10 months ago)
Expires March 27, 2030 (3 years, 6 months)
Last Updated November 15, 2022
Name Servers amir.ns.cloudflare.com, jo.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2.16.245.169
ASN AS20940 (AKAMAI-ASN1, NL)
Provider Akamai
Data source: rdap (0.3s)

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 123 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
34 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
36 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
123 ms
Total Time Total request time from DNS lookup through full response.
124 ms

Connection waterfall

DNS Lookup 34 ms TCP Connect 16 ms TLS Handshake 36 ms Server Processing 37 ms Content Transfer 0 ms
A+
Health Check Endpoint
Auth-protected health endpoint at https://Defacto.com/health (HTTP 403)
PASS
Auth-protected health endpoint at https://Defacto.com/health (HTTP 403)
Info::
Auth-protected health endpoint exposed at https://Defacto.com/health
Got: https://Defacto.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback