Skip to content
https://inverse.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
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.inverse.com/
200https://inverse.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://inverse.com/ → https://inverse.com/

Consistent

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

Certificate validity

311
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
CDN & Delivery
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD56-P5)
Got: x-amz-cf-id: qYwqYxZNhmYrAL329yCory-572IIKqsIWsexAQuTBohzAOXdvb8mLg==
Info::
CDN cache status: FunctionGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status FunctionGeneratedResponse from cloudfront Evidence x-amz-cf-id: qYwqYxZNhmYrAL329yCory-572IIKqsIWsexAQuTBohzAOXdvb8mLg==
A+
DNS Records
4 A records, 45 ms lookup
PASS
4 A records, 45 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 3.174.180.60, 3.174.180.62, 3.174.180.86, 3.174.180.23
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1937.awsdns-50.co.uk, ns-1212.awsdns-23.org, ns-444.awsdns-55.com, ns-834.awsdns-40.net
Info::
5 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: 45 ms
Got: 45 ms
A3.174.180.60, 3.174.180.62, 3.174.180.86, 3.174.180.23
AAAA—
CNAME—
NSns-1937.awsdns-50.co.uk, ns-1212.awsdns-23.org, ns-444.awsdns-55.com, ns-834.awsdns-40.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
google-site-verification=MOFZ8cp38PrCwvkSkgAZNKbSIAI9rBBKaNM-IzVhBJc
google-site-verification=a0p2gelplBe5BtdgUjAbJaMB77C9x1O3xkw9hMzNnCc
_globalsign-domain-verification=95YZs-Lq6mpDrrS5bnsvxSp8Llz8ZsgkwBGGx8RQVh
pinterest-site-verification=9899003aeae505c69a2bb84e5e9a73c4
google-site-verification=jnKRZvLjYIWQNtIIyndjLSsXyWaGQNzimj608qFSt_k
google-site-verification=3hH1qd9cUMCSWCf2u2WSiQid-eON9zhCep-FAmuoPks
google-site-verification=4I-1OVCQWR3qLd9fzumD2t3RvimpcMI8L-thSz7LN_s
facebook-domain-verification=1q4ginek8aby5a9wri1xcawzbphur1
yandex-verification: 2d3b9c7756e24f9c
google-site-verification=yL2f3lJMnTcISGMcPGCGqTefYuVhYdZYfa5NVZu3c-0
SPF v=spf1 include:_spf.google.com include:amazonses.com ~all
_globalsign-domain-verification=GXpUUS49HB9rYWZEmxJFtZdS61weLMlf91w9Dn-5O0
brave-ledger-verification=e66dd15ff9c90b5c164ea4ba48167d7a2deee63bfb8a09cf5a0d04...
CAALookup not available with standard resolver
Resolved in 45 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), 81 ms total
PASS
1 redirect(s), 81 ms total
Info::
Single redirect
Got: https://inverse.com → https://www.inverse.com (301)
Info::
WWW normalization redirect

https://inverse.com

7 ms · HTTP/1.1

301

https://www.inverse.com

74 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://inverse.com3017 msHTTP/1.1CloudFront
2https://www.inverse.com20074 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 158 URLs
PASS
robots.txt present, sitemap with 158 URLs
Info::
robots.txt is present
Got: 288 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 158 entries
Info::
Sitemap index with 158 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 288 B Sitemaps referenced 2 User-agents NewsWhipbot, *, Applebot, Applebot-Extended Blocking No — crawling allowed
User-agent: *
Disallow: 
Disallow: /search?*

User-agent: Applebot
User-agent: Applebot-Extended
User-agent: NewsWhipbot
Disallow: /

Sitemap: https://www.inverse.com/sitemaps/pages.xml
Sitemap: https://www.inverse.com/sitemaps/news.xml

License: https://rslcollective.org/attribution.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 158 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
inverse.com — via Amazon Registrar, Inc., 24 years, 9 months old, hosted on AWS
PASS
inverse.com — via Amazon Registrar, Inc., 24 years, 9 months old, hosted on AWS
Info::
Domain registered until Nov 8, 2030 (4 years, 7 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: Amazon Registrar, Inc.
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

1574 days

November 8, 2030

SSL certificate

311 days

Issued by Amazon

Domain age

24 years, 9 months

Registered November 8, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.174.180.23

Registrar

Amazon Registrar, Inc.

Unlocked 4 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 Amazon Registrar, Inc.
Created November 8, 2001 (24 years, 9 months ago)
Expires November 8, 2030 (4 years, 7 months)
Last Updated November 9, 2022
Name Servers ns-1212.awsdns-23.org, ns-1937.awsdns-50.co.uk, ns-444.awsdns-55.com, ns-834.awsdns-40.net
DNSSEC Not enabled
Hosting
IP Address 3.174.180.23
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 51 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
39 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
51 ms
Total Time Total request time from DNS lookup through full response.
51 ms

Connection waterfall

DNS Lookup 39 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 7 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