Skip to content
https://awin1.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 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: 331 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 331 B Sitemaps referenced 0 User-agents *, Googlebot Blocking No — crawling allowed
# For all robots

User-agent: *


# Disallow indexing of redirect pages

Disallow:	/tclick.php

Disallow:	/awclick.php

Disallow:	/bclick.php

Disallow:	/awshow.php

Disallow:	/show.php

Disallow:	/pclick.php

Disallow:	/cread.php

Disallow:	/swclick.php


# For googlebot

User-agent: Googlebot


# Allow EVERYTHING

Allow: /


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://awin1.com/ http://www.awin.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 28 ms lookup
PASS
4 A records, 28 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 65.8.202.83, 65.8.202.69, 65.8.202.76, 65.8.202.24
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1580.awsdns-05.co.uk, ns-680.awsdns-21.net, ns-122.awsdns-15.com, ns-1365.awsdns-42.org
Info::
1 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: 28 ms
Got: 28 ms
A65.8.202.83, 65.8.202.69, 65.8.202.76, 65.8.202.24
AAAA
CNAME
NSns-1580.awsdns-05.co.uk, ns-680.awsdns-21.net, ns-122.awsdns-15.com, ns-1365.awsdns-42.org
MX
0 awin1-com.mail.protection.outlook.com
TXT
MS=ms92252180
_globalsign-domain-verification=xfkrv3yRwA5GGm0E4l5RlcNKTqVD8KAYsYdCYTBMF0
SPF v=spf1 include:spf.protection.outlook.com -all
CAALookup not available with standard resolver
Resolved in 28 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), 191 ms total
PASS
1 redirect(s), 191 ms total
Info::
Single redirect
Got: https://awin1.com → https://www.awin.com/ (301)
Info::
WWW normalization redirect
Info::
Cross-domain redirect detected

https://awin1.com

27 ms · HTTP/1.1

301

https://www.awin.com/

164 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://awin1.com30127 msHTTP/1.1AkamaiGHost
2https://www.awin.com/200164 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
awin1.com — via Amazon Registrar, Inc., 26 years, 3 months old, hosted on AWS
PASS
awin1.com — via Amazon Registrar, Inc., 26 years, 3 months old, hosted on AWS
Info::
Domain registered until May 19, 2027 (1 years, 1 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

307 days

May 19, 2027

SSL certificate

99 days

Issued by Amazon

Domain age

26 years, 3 months

Registered May 19, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

65.8.202.24

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 May 19, 2000 (26 years, 3 months ago)
Expires May 19, 2027 (1 years, 1 months)
Last Updated April 14, 2026
Name Servers ns-122.awsdns-15.com, ns-1365.awsdns-42.org, ns-1580.awsdns-05.co.uk, ns-680.awsdns-21.net
DNSSEC Not enabled
Hosting
IP Address 65.8.202.24
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 62 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
45 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.
63 ms
Total Time Total request time from DNS lookup through full response.
63 ms

Connection waterfall

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

Send Feedback