Skip to content
https://bgr.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
3
PASS
6
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
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
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.bgr.com/
200https://bgr.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

81
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, 198 ms lookup
PASS
4 A records, 198 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 99.86.20.59, 99.86.20.118, 99.86.20.80, 99.86.20.116
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1194.awsdns-21.org, ns-122.awsdns-15.com, ns-1993.awsdns-57.co.uk, ns-722.awsdns-26.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: 198 ms
Got: 198 ms
A99.86.20.59, 99.86.20.118, 99.86.20.80, 99.86.20.116
AAAA—
CNAME—
NSns-1194.awsdns-21.org, ns-122.awsdns-15.com, ns-1993.awsdns-57.co.uk, ns-722.awsdns-26.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
TXT
google-site-verification=n4u3nROK81U8Ln-ho2RZLoU_VMr3d_JOGImyvjoK9C0
spf2.0/pra include:_spf.google.com ~all
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 198 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), 259 ms total
PASS
1 redirect(s), 259 ms total
Info::
Single redirect
Got: https://bgr.com → https://www.bgr.com/ (301)
Info::
WWW normalization redirect

https://bgr.com

130 ms · HTTP/1.1

301

https://www.bgr.com/

128 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bgr.com301130 msHTTP/1.1nginx/1.18.0 (Ubuntu)
2https://www.bgr.com/200128 msHTTP/1.1nginx/1.18.0 (Ubuntu)

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 66 URLs
PASS
robots.txt present, sitemap with 66 URLs
Info::
robots.txt is present
Got: 245 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 66 entries
Info::
Sitemap index with 66 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 245 B Sitemaps referenced 2 User-agents Googlebot, * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Disallow: /wp-includes/

Disallow: /*?*ajax=

Disallow: /search/


User-agent: Googlebot

Disallow: /sponsored/


Sitemap: https://www.bgr.com/sitemap_index.xml

Sitemap: https://www.bgr.com/?getfeed=google
sitemap.xml 200 OK
Type Sitemap Index URLs 66 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
bgr.com — via GoDaddy.com, LLC, 23 years, 4 months old, hosted on AWS
PASS
bgr.com — via GoDaddy.com, LLC, 23 years, 4 months old, hosted on AWS
Info::
Domain registered until Apr 21, 2027 (1 years 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

310 days

April 21, 2027

SSL certificate

81 days

Issued by Amazon

Domain age

23 years, 4 months

Registered April 21, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

99.86.20.80

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created April 21, 2003 (23 years, 4 months ago)
Expires April 21, 2027 (1 years)
Last Updated June 25, 2025
Name Servers ns-1194.awsdns-21.org, ns-122.awsdns-15.com, ns-1993.awsdns-57.co.uk, ns-722.awsdns-26.net
DNSSEC Not enabled
Hosting
IP Address 99.86.20.80
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

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 127 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
104 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.
128 ms
Total Time Total request time from DNS lookup through full response.
128 ms

Connection waterfall

DNS Lookup 104 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 19 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: SIN3-P2)
Got: x-amz-cf-id: RAde6aJDzAbRrl8bg9CuEdeMzsplzOE30wZ1gkXaBYVIPRoBlWPO9A==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: RAde6aJDzAbRrl8bg9CuEdeMzsplzOE30wZ1gkXaBYVIPRoBlWPO9A==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback