Skip to content
https://inquirer.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.inquirer.com/
200https://inquirer.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://inquirer.com/ → https://www.inquirer.com:443/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
2 A records, 129 ms lookup
PASS
2 A records, 129 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 52.223.20.214, 35.71.148.62
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-792.awsdns-35.net, ns-1234.awsdns-26.org, ns-205.awsdns-25.com, ns-1676.awsdns-17.co.uk
Info::
4 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 129 ms
Got: 129 ms
A52.223.20.214, 35.71.148.62
AAAA—
CNAME—
NSns-792.awsdns-35.net, ns-1234.awsdns-26.org, ns-205.awsdns-25.com, ns-1676.awsdns-17.co.uk
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 alt3.aspmx.l.google.com
TXT
google-site-verification=1dIGJdjAs2lZ_caRLqcA1bpUGj5XsBxh4ghYY6pvxK4
miro-verification=0708b1ef4005fb1d553fde59dbb73d01e2272f1b
amazonses:GPrIAIUR6g8/MmcmuZSFKvCPJCGb3IsmELegL4J4KCQ=
facebook-domain-verification=lacdwv1oor6frylkk0ek78z0em7sg9
apple-domain-verification=d-lHRBn-OwQcvWlGGLU61ClekO1Uwd6hDN7Fe8yTrAU
adobe-idp-site-verification=7d0f6864c606f0fbb47cc6e0221ce184c6fc8e695d2d8ec3051c...
google-site-verification=l8Yldhs2aLnaQ7xHLXB8JY2FufQZJGCaAdlAMQ-ST_Q
anthropic-domain-verification-acpz9g=2mTlxyQXmsdevETvYM4EE17yY
tollbit-domain-verification=44d2cc7076de1a7fc6625fcbce88457ebc6532c6412d8063867f...
google-site-verification=G5S1oaTre6cJQmOIG72bXIM7C5XnvZXMkjqdCfUWI8E
canva-site-verification=55bupCph3wh8g450e5YyIQ
smartsheet-site-validation=BDTPtBaV4GQcuqvfQHCKk8tCEu305o7y
google-site-verification=6oo9TYIFgkX16J0T_7uHHCGJ6vR5jAvMOyqhtr-lWT8
ZOOM_verify_Hk8WyfqA3H2MY3KozyrYmV
pinterest-site-verification=c78bdc9fc29b17107b1d98d5bf5ca13e
google-site-verification=1AEGqFeZuNWpnchbpUhj6RgXB10elX70mgJ1HKTF670
google-site-verification=cUL0VdYj2WKZc69hCuKQ7Gme02xv-RDhrGquZvm8o8M
MS=ms34149025
9eja1c290rd3q7uopcht1tg72a
SPF v=spf1 include:_spf.google.com include:amazonses.com include:servers.mcsv.net in...
CAALookup not available with standard resolver
Resolved in 129 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 718 ms total
PASS
1 redirect(s), 718 ms total
Info::
Single redirect
Got: https://inquirer.com → https://www.inquirer.com:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 718 ms total
Got: 718 ms

https://inquirer.com

127 ms · HTTP/1.1

301

https://www.inquirer.com:443/

592 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://inquirer.com301127 msHTTP/1.1awselb/2.0
2https://www.inquirer.com:443/200592 msHTTP/1.1openresty

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 88 URLs
PASS
robots.txt present, sitemap with 88 URLs
Info::
robots.txt is present
Got: 547 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 88 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 547 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /light/
Disallow: /search
Disallow: /sports/betting/
Disallow: /wires/
Disallow: /Preview/
Disallow: /zzz-systest/
Disallow: /zzz_systest/
Disallow: */zzz-systest/
Disallow: */zzz_systest/
Disallow: */zzz_systest/

Sitemap: https://www.inquirer.com/sitemaps/48hour-news-sitemap-partner.xml
Sitemap: https://www.inquirer.com/arc/outboundfeeds/sitemap-index-2/?outputType=xml
Sitemap: https://www.inquirer.com/arc/outboundfeeds/sitemap-restaurant-page/
Sitemap: https://www.inquirer.com/arc/outboundfeeds/sitemap-author-page/
sitemap.xml 200 OK
Type URL Set URLs 88 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
inquirer.com — via GoDaddy.com, LLC, 31 years, 4 months old, hosted on AWS
PASS
inquirer.com — via GoDaddy.com, LLC, 31 years, 4 months old, hosted on AWS
Info::
Domain registered until May 30, 2030 (4 years, 1 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: AWS
Got: AS16509
Domain expiry

1444 days

May 30, 2030

SSL certificate

317 days

Issued by Amazon

Domain age

31 years, 4 months

Registered May 31, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.223.20.214

Registrar

GoDaddy.com, LLC

Unlocked 3 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 May 31, 1995 (31 years, 4 months ago)
Expires May 30, 2030 (4 years, 1 months)
Last Updated September 4, 2022
Name Servers ns-1234.awsdns-26.org, ns-205.awsdns-25.com, ns-792.awsdns-35.net
DNSSEC Not enabled
Hosting
IP Address 52.223.20.214
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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 163 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
48 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
28 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
58 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
164 ms
Total Time Total request time from DNS lookup through full response.
164 ms

Connection waterfall

DNS Lookup 48 ms TCP Connect 28 ms TLS Handshake 58 ms Server Processing 29 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback