Skip to content
https://psy.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
6 PASS 10 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.

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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 46.105.204.30 does not match any cert SAN: cluster030.hosting.cdn.ovh.net
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.
B
Multi-Resolver DNS Speed
Mean 106ms across 3 resolvers (spread 95ms)
REVIEW
Mean 106ms across 3 resolvers (spread 95ms)
Info::
Google: 44ms
Got: 44ms via 8.8.8.8:53
Info::
Cloudflare: 135ms
Got: 135ms via 1.1.1.1:53
Info::
Quad9: 139ms
Got: 139ms via 9.9.9.9:53
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: 408 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 408 B Sitemaps referenced 0 User-agents Mediapartners-Google, *, Googlebot Blocking No — crawling allowed
User-agent: Mediapartners-Google
Disallow:

User-agent: *
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /wp-content/uploads/
Disallow: */xmlrpc.php
Disallow: */wp-*.php
Disallow: */trackback/
Disallow: *?wptheme=
Disallow: *?comments=
Disallow: *?replytocom
Disallow: */comment-page-
Disallow: *?s=
Disallow: */taxonomy/term/
Disallow: */comment/reply/

User-Agent: Googlebot
Allow: .js
Allow: .css

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
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.psy.it/
200https://psy.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://psy.it/ https://psy.it/

Consistent

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

Certificate validity

49
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
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: 404, /health: 404, /healthz: 500, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 65 ms lookup
PASS
1 A records, 65 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 46.105.204.30
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns4.arubadns.cz, dns2.technorail.com, dns.technorail.com, dns3.arubadns.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 65 ms
Got: 65 ms
A46.105.204.30
AAAA
CNAME
NSdns4.arubadns.cz, dns2.technorail.com, dns.technorail.com, dns3.arubadns.net
MX
10 psy-it.mail.protection.outlook.com
TXT
cisco-ci-domain-verification=64d65fe39dfe9b43222be88cbbeb4c3cfa1672190da4e4858ea...
SPF v=spf1 ip4:37.153.135.8 ip4:45.86.144.55 ip4:161.97.142.240 ip6:2a02:c206:2074:1...
MS=ms91600588
cisco-ci-domain-verification=734dd251898f41e3fa943dc41a7a7d2ed101e43e9b5470a48b1...
brevo-code:54ac3be31c9d9970ee7e4dea9759c872
CAALookup not available with standard resolver
Resolved in 65 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Redirect Chain
1 redirect(s), 311 ms total
PASS
1 redirect(s), 311 ms total
Info::
Single redirect
Got: https://psy.it → https://www.psy.it/ (301)
Info::
WWW normalization redirect

https://psy.it

242 ms · HTTP/1.1

301

https://www.psy.it/

69 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://psy.it301242 msHTTP/1.1
2https://www.psy.it/20069 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
psy.it — via ARUBA-REG, 30 years, 10 months old, hosted on OVH
PASS
psy.it — via ARUBA-REG, 30 years, 10 months old, hosted on OVH
Info::
Domain registered until Nov 5, 2026 (3 months remaining)
Info::
Registrar: ARUBA-REG
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: OVH
Got: AS16276
Domain expiry

116 days

November 5, 2026

SSL certificate

49 days

Issued by Let's Encrypt

Domain age

30 years, 10 months

Registered January 29, 1996

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

46.105.204.30

Registrar

ARUBA-REG

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar ARUBA-REG
Created January 29, 1996 (30 years, 10 months ago)
Expires November 5, 2026 (3 months)
Last Updated November 21, 2025
Name Servers dns.technorail.com, dns2.technorail.com, dns3.arubadns.net, dns4.arubadns.cz
Registrant Consiglio Nazionale Ordine Psicologi
Hosting
IP Address 46.105.204.30
ASN AS16276 (OVH - OVH SAS, FR)
Provider OVH
Data source: whois (0.9s)

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 275 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
54 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
19 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
275 ms
Total Time Total request time from DNS lookup through full response.
275 ms

Connection waterfall

DNS Lookup 54 ms TCP Connect 19 ms TLS Handshake 24 ms Server Processing 178 ms Content Transfer 0 ms
A+
CDN Cache Observability
Cache state: fresh (Age=0)
PASS
Cache state: fresh (Age=0)
Info::
CDN cache state observable via 1 header(s)
Got: age=0
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback