Skip to content
https://fwmrm.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1116 ms total
FIX
2 redirect(s), 1116 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1116 ms total
Got: 1116 ms
Info::
Cross-domain redirect detected

https://fwmrm.net

258 ms · HTTP/1.1

301

https://freewheel.com:443/

438 ms · HTTP/1.1

301

https://www.freewheel.com/

419 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fwmrm.net301258 msHTTP/1.1awselb/2.0
2https://freewheel.com:443/301438 msHTTP/1.1cloudflare
3https://www.freewheel.com/200419 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

Certificate validity

227
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
2 A records, 5 ms lookup
PASS
2 A records, 5 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 13.248.238.180, 99.83.195.29
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
Info::
2 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: 5 ms
Got: 5 ms
A13.248.238.180, 99.83.195.29
AAAA
CNAME
NSdns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
MX
10 mxa-00143702.gslb.pphosted.com
10 mxb-00143702.gslb.pphosted.com
TXT
MS=ms61939404
_a25kphnvxut3z7gmtxb26c5csj55py2
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
CAALookup not available with standard resolver
Resolved in 5 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+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 191 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
Sitemap index with 7 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 191 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
Crawl-delay: 10
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.freewheel.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
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.fwmrm.net/
200https://fwmrm.net/

Preferred variant: non-www

HTTP → HTTPS

301http://fwmrm.net/ https://fwmrm.net:443/

Consistent

A+
Domain Intelligence
fwmrm.net — via CSC Corporate Domains, Inc., 18 years, 8 months old, hosted on AWS
PASS
fwmrm.net — via CSC Corporate Domains, Inc., 18 years, 8 months old, hosted on AWS
Info::
Domain registered until Nov 13, 2032 (6 years, 8 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: CSC Corporate Domains, 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

2343 days

November 13, 2032

SSL certificate

227 days

Issued by DigiCert Inc

Domain age

18 years, 8 months

Registered November 13, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.248.238.180

Registrar

CSC Corporate Domains, 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 CSC Corporate Domains, Inc.
Created November 13, 2007 (18 years, 8 months ago)
Expires November 13, 2032 (6 years, 8 months)
Last Updated July 2, 2025
Name Servers dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
DNSSEC Not enabled
Hosting
IP Address 13.248.238.180
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 260 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 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.
168 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
260 ms
Total Time Total request time from DNS lookup through full response.
260 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 1 ms TLS Handshake 168 ms Server Processing 84 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