Skip to content
https://flic.kr

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 3 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 33 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 33 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /g/4arE9C
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

256
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
A
DNS Records
4 A records, 294 ms lookup
PASS
4 A records, 294 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 52.222.132.107, 52.222.132.39, 52.222.132.63, 52.222.132.123
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1832.awsdns-37.co.uk, ns-739.awsdns-28.net, ns-1394.awsdns-46.org, ns-252.awsdns-31.com
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (294 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 294 ms
A52.222.132.107, 52.222.132.39, 52.222.132.63, 52.222.132.123
AAAA
CNAME
NSns-1832.awsdns-37.co.uk, ns-739.awsdns-28.net, ns-1394.awsdns-46.org, ns-252.awsdns-31.com
MX
TXT
CAALookup not available with standard resolver
Resolved in 294 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.

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)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://flic.kr

https://flic.kr

128 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://flic.kr200128 msHTTP/1.1
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.flic.kr/
200https://flic.kr/

HTTP → HTTPS

301http://flic.kr/ https://flic.kr/

Consistent

A+
Domain Intelligence
flic.kr — via Gabia, Inc.(http://www.gabia.co.kr), hosted on AWS
PASS
flic.kr — via Gabia, Inc.(http://www.gabia.co.kr), hosted on AWS
Info::
Registrar: Gabia, Inc.(http://www.gabia.co.kr)
Info::
Hosting: AWS
Got: AS16509
Domain expiry

Unknown

SSL certificate

256 days

Issued by Amazon

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.222.132.39

Registrar

Gabia, Inc.(http://www.gabia.co.kr)

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar Gabia, Inc.(http://www.gabia.co.kr)
Name Servers ns-1394.awsdns-46.org, ns-1832.awsdns-37.co.uk, ns-252.awsdns-31.com, ns-739.awsdns-28.net
Hosting
IP Address 52.222.132.39
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (1.6s)
A+
HTTP Probe Timing
Total 167 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
31 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.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
167 ms
Total Time Total request time from DNS lookup through full response.
168 ms

Connection waterfall

DNS Lookup 31 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 132 ms Content Transfer 1 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD53-P7)
Got: x-amz-cf-id: EE-gXIXOUVSzp7GmMw_8wpuCrDL7UfR86L-a2-RKqXw4Lfz3KXvrUA==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: EE-gXIXOUVSzp7GmMw_8wpuCrDL7UfR86L-a2-RKqXw4Lfz3KXvrUA==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback