Skip to content
https://www.gov.ie

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
3
PASS
5
INFO
1
Probed from Sao Paulo, Brazil
302 Found
Checks
9
5 PASS 3 REVIEW
B
DNS Records
4 A records, 206 ms lookup
REVIEW
4 A records, 206 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 108.156.85.30, 108.156.85.62, 108.156.85.93, 108.156.85.16
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: d2oos2jwwtfbjj.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-1077.awsdns-06.org, ns-140.awsdns-17.com, ns-1742.awsdns-25.co.uk, ns-572.awsdns-07.net
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 (206 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 206 ms
A108.156.85.30, 108.156.85.62, 108.156.85.93, 108.156.85.16
AAAA—
CNAMEd2oos2jwwtfbjj.cloudfront.net
NSns-1077.awsdns-06.org, ns-140.awsdns-17.com, ns-1742.awsdns-25.co.uk, ns-572.awsdns-07.net
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 206 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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

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
157 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
Redirect Chain
1 redirect(s), 689 ms total
PASS
1 redirect(s), 689 ms total
Info::
Single redirect
Got: https://www.gov.ie → https://www.gov.ie/en/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.gov.ie
Info::
Redirect overhead: 689 ms total
Got: 689 ms

https://www.gov.ie

340 ms · HTTP/1.1

302

https://www.gov.ie/en/

349 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.gov.ie302340 msHTTP/1.1gunicorn
2https://www.gov.ie/en/200349 msHTTP/1.1gunicorn

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 24 URLs
PASS
robots.txt present, sitemap with 24 URLs
Info::
robots.txt is present
Got: 293 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 24 entries
Info::
Sitemap index with 24 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 293 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /admin/
Disallow: /django-admin/
Disallow: /documents/
Disallow: /search/
Disallow: /*/search/
Disallow: /cuardaigh/
Disallow: /*/cuardaigh/
# Blocks numerous Irish search pages
Disallow: /*?*
Allow: /static/

# Point to sitemap
Sitemap: https://www.gov.ie/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 24 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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.gov.ie/
301https://gov.ie/

Preferred variant: www

HTTP → HTTPS

301http://www.gov.ie/ → https://www.gov.ie/

Consistent

A+
HTTP Probe Timing
Total 334 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
8 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
107 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
110 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
334 ms
Total Time Total request time from DNS lookup through full response.
334 ms

Connection waterfall

DNS Lookup 8 ms TCP Connect 107 ms TLS Handshake 110 ms Server Processing 109 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MIA3-P2)
Got: x-amz-cf-id: V4uNNrApgQt8XXvE-g0zqDQrBZdcNd9HAMB8igTI8aYiD1NYrAuNZA==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: V4uNNrApgQt8XXvE-g0zqDQrBZdcNd9HAMB8igTI8aYiD1NYrAuNZA==
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback