Skip to content
https://msmgraphs.org

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
3
REVIEW
7
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
17
7 PASS 7 REVIEW 3 FIX
D
Multi-Resolver DNS Speed
Action
Mean 130ms across 3 resolvers (spread 327ms)
FIX
Mean 130ms across 3 resolvers (spread 327ms)
Info::
Cloudflare: 12ms
Got: 12ms via 1.1.1.1:53
Info::
Google: 39ms
Got: 39ms via 8.8.8.8:53
Info::
Quad9: 339ms
Got: 339ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 327ms (min 12ms / max 339ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
D
HTTP Probe Timing
Action
Total 2122 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
63 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
8 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
18 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.64 s
Total Time Total request time from DNS lookup through full response.
2.12 s

Connection waterfall

DNS Lookup 63 ms TCP Connect 8 ms TLS Handshake 18 ms Server Processing 1.55 s Content Transfer 480 ms
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 84.32.84.205: lookup 84.32.84.205: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR for 88.222.222.114 does not match any cert SAN: 88-222-222-114.init.lt
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR lookup failed for 2a02:4780:84:ac8f:3dd2:39d8:f8a6:3c6e: lookup 2a02:4780:84:ac8f:3dd2:39d8:f8a6:3c6e: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2a02:4780:84:88b8:57f8:fe5f:911:15c0: lookup 2a02:4780:84:88b8:57f8:fe5f:911:15c0: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
69 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

69
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
2 A records, 248 ms lookup
PASS
2 A records, 248 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 84.32.84.205, 88.222.222.114
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:4780:84:ac8f:3dd2:39d8:f8a6:3c6e, 2a02:4780:84:88b8:57f8:fe5f:911:15c0
Info::
2 nameserver(s) configured
Got: ns2.dns-parking.com, ns1.dns-parking.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (248 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 248 ms
A84.32.84.205, 88.222.222.114
AAAA2a02:4780:84:ac8f:3dd2:39d8:f8a6:3c6e, 2a02:4780:84:88b8:57f8:fe5f:911:15c0
CNAME—
NSns2.dns-parking.com, ns1.dns-parking.com
MX
5 mx1.hostinger.in
10 mx2.hostinger.in
TXT
SPF v=spf1 include:_spf.mail.hostinger.com ~all
CAALookup not available with standard resolver
Resolved in 248 ms

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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://msmgraphs.org

https://msmgraphs.org

1462 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://msmgraphs.org2001462 msHTTP/1.1hcdn
A+
IPv6 Readiness
IPv6 reachable (222 ms)
PASS
IPv6 reachable (222 ms)
Info::
IPv6 is configured and reachable at 2a02:4780:84:ac8f:3dd2:39d8:f8a6:3c6e, 2a02:4780:84:88b8:57f8:fe5f:911:15c0
Got: 222 ms connect
IPv6 Ready
AAAA Records 2a02:4780:84:ac8f:3dd2:39d8:f8a6:3c6e, 2a02:4780:84:88b8:57f8:fe5f:911:15c0 Connection Reachable (222 ms)
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 87 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 87 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /wp-admin

Sitemap: https://msmgraphs.org/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 7 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::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.msmgraphs.org/
200https://msmgraphs.org/

HTTP → HTTPS

301http://msmgraphs.org/ → https://msmgraphs.org/

Consistent

A
Domain Intelligence
msmgraphs.org — via PDR Ltd. d/b/a PublicDomainRegistry.com, 1 years, 10 months old
PASS
msmgraphs.org — via PDR Ltd. d/b/a PublicDomainRegistry.com, 1 years, 10 months old
Warning::
Domain expires in 45 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Oct 29, 2026
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: PDR Ltd. d/b/a PublicDomainRegistry.com
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.
Domain expiry

39 days

October 29, 2026

SSL certificate

69 days

Issued by Let's Encrypt

Domain age

1 years, 10 months

Registered October 29, 2024

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:4780:4c:d8a5:8283:8ec7:c84c:892d

Registrar

PDR Ltd. d/b/a PublicDomainRegistry.com

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar PDR Ltd. d/b/a PublicDomainRegistry.com
Created October 29, 2024 (1 years, 10 months ago)
Expires October 29, 2026 (1 months)
Last Updated August 12, 2026
Name Servers ns1.dns-parking.com, ns2.dns-parking.com
DNSSEC Not enabled
Hosting
IP Address 2a02:4780:4c:d8a5:8283:8ec7:c84c:892d
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Send Feedback