Skip to content
https://myanimelist.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
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
276 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

276
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+
DNS Records
2 A records, 4 ms lookup
PASS
2 A records, 4 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 23.209.46.96, 23.209.46.93
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a7-64.akam.net, a3-64.akam.net, a4-65.akam.net, a12-67.akam.net, a10-66.akam.net, a1-154.akam.net
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: 4 ms
Got: 4 ms
A23.209.46.96, 23.209.46.93
AAAA—
CNAME—
NSa7-64.akam.net, a3-64.akam.net, a4-65.akam.net, a12-67.akam.net, a10-66.akam.net, a1-154.akam.net
MX
10 inbound-smtp.us-west-2.amazonaws.com
TXT
atlassian-domain-verification=JthYOOYykJQvEGsbFO8W4SmNmeqP1UPRVqBju2abSTvCidh1cN...
amazonses:kUdjxXbwajsFpjgJkXMynd2nnHf94C2nanY9RW8jjB8=
SPF v=spf1 +a:smtp1.myanimelist.net +a:smtp2.myanimelist.net include:mail.zendesk.co...
google-site-verification=PpITtKzX5t45mJKLvLu0_SsRawpHGiVtnHv4xZr997w
google-site-verification=C-PFnwikvQ366aZC372JDYCqewOIyurJhR-FqQ7l700
google-site-verification=lfaNU5RPhI7t0ZETvrR-rfL48r0W-bXv9SQHTOLd4GY
google-site-verification=HqzKDqsseElTV0Jd-q4kuUHxcIYyYww1EQuUAuehbPM
google-site-verification=vI_8vq-t_KULxSJR4I3Lftt4_Nfpq8OgC6YRUc6Px5Q
facebook-domain-verification=wgjc97kugs1ga56gkwt61le6qmphi3
CAALookup not available with standard resolver
Resolved in 4 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://myanimelist.net

https://myanimelist.net

377 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://myanimelist.net200377 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 1752 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
Sitemap index with 13 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1752 B Sitemaps referenced 1 User-agents FacebookBot, ISSCyberRiskCrawler, Kangaroo Bot, YandexAdditional, Bytespider, *, AI2Bot, ChatGLM-Spider, cohere-training-data-crawler, Cotoyogi, Diffbot, FirecrawlAgent, ICC-Crawler, meta-externalagent, omgili, omgilibot, Scrapy, Sidetrade indexer bot, Timpibot, VelenPublicWebCrawler, Webzio-Extended, Google-Extended, GPTBot, laion-huggingface-processor, Spider, YandexAdditionalBot, LAIONDownloader, DeepSeekBot, facebookexternalhit, Factset_spyderbot, SBIntuitionsBot, webzio-extended, anthropic-ai, Brightbot 1.0, Meta-ExternalAgent, Ai2Bot-Dolma, Applebot-Extended, Claude-Web, FriendlyCrawler, Linguee Bot, PanguBot, ClaudeBot, img2dataset, TerraCotta, TikTokSpider, aiHitBot, CCBot Blocking No — crawling allowed
User-agent: *
Disallow: /admin/
Disallow: /log/
Disallow: /includes/
Disallow: /comtocom.php
Disallow: /comments.php
Disallow: /ad/
Disallow: /about
Disallow: /dbchanges.php
Disallow: /clubs.php/*
Disallow: /_Incapsula_Resource
Disallow: /mymessages.php
Disallow: /sns/*/*

# Block crawlers used for AI/LLM training data collection
User-agent: AI2Bot
User-agent: Ai2Bot-Dolma
User-agent: aiHitBot
User-agent: anthropic-ai
User-agent: Applebot-Extended
User-agent: Brightbot 1.0
User-agent: CCBot
User-agent: ChatGLM-Spider
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: cohere-training-data-crawler
User-agent: Cotoyogi
User-agent: DeepSeekBot
User-agent: Diffbot
User-agent: FacebookBot
User-agent: facebookexternalhit
User-agent: Factset_spyderbot
User-agent: FirecrawlAgent
User-agent: FriendlyCrawler
User-agent: Google-Extended
User-agent: GPTBot
User-agent: ICC-Crawler
User-agent: img2dataset
User-agent: ISSCyberRiskCrawler
User-agent: Kangaroo Bot
User-agent: laion-huggingface-processor
User-agent: LAIONDownloader
User-agent: Linguee Bot
User-agent: Meta-ExternalAgent
User-agent: meta-externalagent
User-agent: omgili
User-agent: omgilibot
User-agent: PanguBot
User-agent: SBIntuitionsBot
User-agent: Scrapy
User-agent: Sidetrade indexer bot
User-agent: Spider
User-agent: TerraCotta
User-agent: TikTokSpider
User-agent: Timpibot
User-agent: VelenPublicWebCrawler
User-agent: Webzio-Extended
User-agent: webzio-extended
User-agent: YandexAdditional
User-agent: YandexAdditionalBot
Disallow: /

# Bytespider requires its own separate block as it ignores grouped directives
# Reference: https://github.com/ai-robots-txt/ai.robots.txt/issues/108
User-agent: Bytespider
Disallow: /

Sitemap: https://myanimelist.net/sitemap/index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 13 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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.myanimelist.net/
200https://myanimelist.net/

Preferred variant: non-www

HTTP → HTTPS

301http://myanimelist.net/ → https://myanimelist.net:443/

Consistent

A+
Domain Intelligence
myanimelist.net — via GoDaddy.com, LLC, 20 years, 4 months old, hosted on Akamai
PASS
myanimelist.net — via GoDaddy.com, LLC, 20 years, 4 months old, hosted on Akamai
Info::
Domain registered until Apr 1, 2027 (11 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: 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: Akamai
Got: AS20940
Domain expiry

263 days

April 1, 2027

SSL certificate

276 days

Issued by DigiCert Inc

Domain age

20 years, 4 months

Registered April 1, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS20940

23.209.46.96

Registrar

GoDaddy.com, LLC

Unlocked 6 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 1, 2006 (20 years, 4 months ago)
Expires April 1, 2027 (11 months)
Last Updated March 18, 2026
Name Servers a1-154.akam.net, a10-66.akam.net, a12-67.akam.net, a3-64.akam.net, a4-65.akam.net, a7-64.akam.net
DNSSEC Not enabled
Hosting
IP Address 23.209.46.96
ASN AS20940 (AKAMAI-ASN1, NL)
Provider Akamai
Data source: rdap (0.5s)

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 362 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 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.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
361 ms
Total Time Total request time from DNS lookup through full response.
363 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 352 ms Content Transfer 2 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback