Skip to content
https://infogram.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 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
TLS Certificate Expiry & Recommendations
138 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

138
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
  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
3 A records, 37 ms lookup
PASS
3 A records, 37 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 18.202.40.6, 54.155.242.192, 63.32.160.141
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1095.awsdns-08.org, ns-156.awsdns-19.com, ns-1891.awsdns-44.co.uk, ns-717.awsdns-25.net
Info::
7 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: 37 ms
Got: 37 ms
A18.202.40.6, 54.155.242.192, 63.32.160.141
AAAA—
CNAME—
NSns-1095.awsdns-08.org, ns-156.awsdns-19.com, ns-1891.awsdns-44.co.uk, ns-717.awsdns-25.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
10 aspmx4.googlemail.com
10 aspmx5.googlemail.com
TXT
proxy-ssl.webflow.com
SPF v=spf1 include:_spf.google.com include:mailgun.org include:521303.spf06.hubspote...
CAALookup not available with standard resolver
Resolved in 37 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://infogram.com

https://infogram.com

245 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://infogram.com200245 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 233 URLs
PASS
robots.txt present, sitemap with 233 URLs
Info::
robots.txt is present
Got: 97 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 233 entries
Info::
Sitemap index with 233 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 97 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /app/
Disallow: /oembed
Sitemap: https://infogram.com/sitemaps/index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 233 entries Valid XML Yes
Child Sitemaps:
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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.infogram.com/
200https://infogram.com/

Preferred variant: non-www

HTTP → HTTPS

301http://infogram.com/ → https://infogram.com:443/

Consistent

A+
Domain Intelligence
infogram.com — via Amazon Registrar, Inc., 30 years, 7 months old, hosted on AWS
PASS
infogram.com — via Amazon Registrar, Inc., 30 years, 7 months old, hosted on AWS
Info::
Domain registered until Mar 25, 2027 (11 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

282 days

March 25, 2027

SSL certificate

138 days

Issued by Amazon

Domain age

30 years, 7 months

Registered February 25, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

63.32.160.141

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 February 25, 1996 (30 years, 7 months ago)
Expires March 25, 2027 (11 months)
Last Updated February 18, 2026
Name Servers ns-1095.awsdns-08.org, ns-156.awsdns-19.com, ns-1891.awsdns-44.co.uk, ns-717.awsdns-25.net
DNSSEC Not enabled
Hosting
IP Address 63.32.160.141
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 309 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
28 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
33 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
68 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
242 ms
Total Time Total request time from DNS lookup through full response.
309 ms

Connection waterfall

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

Send Feedback