Skip to content
https://emanuelpina.pt

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
1
REVIEW
5
PASS
11
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
11 PASS 5 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
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 88.99.39.218 does not match any cert SAN: static.218.39.99.88.clients.your-server.de
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 2a01:4f8:c012:2a6b::1: lookup 2a01:4f8:c012:2a6b::1: 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
53 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 44 ms lookup
PASS
1 A records, 44 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 88.99.39.218
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a01:4f8:c012:2a6b::1
Info::
2 nameserver(s) configured
Got: ns2.desec.org, ns1.desec.io
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 44 ms
Got: 44 ms
A88.99.39.218
AAAA2a01:4f8:c012:2a6b::1
CNAME—
NSns2.desec.org, ns1.desec.io
MX
10 in1-smtp.messagingengine.com
20 in2-smtp.messagingengine.com
TXT
google-site-verification=GCx8159EYV3deOS8OeJ0s8GGq8Q6flR3Nv8VlVY1RDI
openpgp4fpr:52DD0B5CF4F6AB67ADC78D7F2E479ED0E3BA5D22
SPF v=spf1 include:spf.messagingengine.com include:_spf.scw-tem.cloud ~all
CAALookup not available with standard resolver
Resolved in 44 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+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A
CAA Records
issue: letsencrypt.org
PASS
issue: letsencrypt.org
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Multi-Resolver DNS Speed
Mean 40ms across 3 resolvers (spread 33ms)
PASS
Mean 40ms across 3 resolvers (spread 33ms)
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Cloudflare: 35ms
Got: 35ms via 1.1.1.1:53
Info::
Quad9: 60ms
Got: 60ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://emanuelpina.pt

https://emanuelpina.pt

95 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://emanuelpina.pt20095 msHTTP/1.1Caddy
A+
IPv6 Readiness
IPv6 reachable (32 ms)
PASS
IPv6 reachable (32 ms)
Info::
IPv6 is configured and reachable at 2a01:4f8:c012:2a6b::1
Got: 32 ms connect
IPv6 Ready
AAAA Records 2a01:4f8:c012:2a6b::1 Connection Reachable (32 ms)
A+
Crawlability
robots.txt present, sitemap with 38 URLs
PASS
robots.txt present, sitemap with 38 URLs
Info::
robots.txt is present
Got: 3812 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 38 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3812 B Sitemaps referenced 1 User-agents CloudVertexBot, Cotoyogi, iaskspider/2.0, omgilibot, YandexAdditional, AmazonBuyForMe, ExaBot, ApifyBot, Awario, imageSpider, LinerBot, MistralAI-User/1.0, Operator, Anomura, Brightbot, EchoboxBot, ICC-Crawler, Kangaroo Bot, Spider, Claude-Code, TikTokSpider, Trae, Brightbot 1.0, Bytespider, newsai, Panscient, QualifiedBot, AzureAI-SearchBot, Google-Agent, LCC, Meta-ExternalFetcher, MistralAI-User, YouBot, Claude-SearchBot, GoogleOther, Thinkbot, AI2Bot, AI2Bot-DeepResearchEval, CCBot, Gemini-Deep-Research, GPTBot, PanguBot, Amzn-SearchBot, FacebookBot, FriendlyCrawler, GoogleOther-Image, img2dataset, Scrapy, anthropic-ai, atlassian-bot, bigsur.ai, kagi-fetcher, TavilyBot, Claude-User, Devin, LAIONDownloader, Webzio-Extended, ZanistaBot, BuddyBot, ChatGLM-Spider, PetalBot, quillbot.com, SemrushBot-SWA, Amazonbot, Aranet-SearchBot, Crawl4AI, DeepSeekBot, Google-CloudVertexBot, KlaviyoAIBot, MyCentralAIScraperBot, Poggio-Citations, Ai2Bot-Dolma, Andibot, Diffbot, Poseidon Research Crawler, Timpibot, wpbot, WRTNBot, ChatGPT-User, GoogleOther-Video, meta-externalfetcher, ShapBot, webzio-extended, Applebot-Extended, NovaAct, QuillBot, YandexAdditionalBot, Echobot Bot, Google-Extended, GoogleAgent-Mariner, TerraCotta, Applebot, bedrockbot, Channel3Bot, Claude-Web, ClaudeBot, Code, cohere-ai, DuckAssistBot, AddSearchBot, KunatoCrawler, laion-huggingface-processor, WARDBot, ApifyWebsiteContentCrawler, Google-Gemini-CLI, NagetBot, Perplexity-User, TwinAgent, Amzn-User, ChatGPT Agent, ISSCyberRiskCrawler, LinkupBot, omgili, Sidetrade indexer bot, Terra Cotta, Bravebot, facebookexternalhit, FirecrawlAgent, HenkBot, OpenAI, panscient.com, PhindBot, aiHitBot, Factset_spyderbot, SBIntuitionsBot, YaK, Cloudflare-AutoRAG, iAskBot, meta-externalagent, netEstate Imprint Crawler, opencode, NotebookLM, OAI-SearchBot, amazon-kendra, Datenbank Crawler, Google-NotebookLM, Linguee Bot, Manus-User, meta-webindexer, SemrushBot-OCOB, *, iaskspider, IbouBot, cohere-training-data-crawler, Crawlspace, Google-Firebase, ImagesiftBot, PerplexityBot, VelenPublicWebCrawler, Meta-ExternalAgent Blocking No — crawling allowed
User-agent: AddSearchBot
User-agent: AI2Bot
User-agent: AI2Bot-DeepResearchEval
User-agent: Ai2Bot-Dolma
User-agent: aiHitBot
User-agent: amazon-kendra
User-agent: Amazonbot
User-agent: AmazonBuyForMe
User-agent: Amzn-SearchBot
User-agent: Amzn-User
User-agent: Andibot
User-agent: Anomura
User-agent: anthropic-ai
User-agent: ApifyBot
User-agent: ApifyWebsiteContentCrawler
User-agent: Applebot
User-agent: Applebot-Extended
User-agent: Aranet-SearchBot
User-agent: atlassian-bot
User-agent: Awario
User-agent: AzureAI-SearchBot
User-agent: bedrockbot
User-agent: bigsur.ai
User-agent: Bravebot
User-agent: Brightbot
User-agent: Brightbot 1.0
User-agent: BuddyBot
User-agent: Bytespider
User-agent: CCBot
User-agent: Channel3Bot
User-agent: ChatGLM-Spider
User-agent: ChatGPT Agent
User-agent: ChatGPT-User
User-agent: Claude-Code
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: Claude-Web
User-agent: ClaudeBot
User-agent: Cloudflare-AutoRAG
User-agent: CloudVertexBot
User-agent: Code
User-agent: cohere-ai
User-agent: cohere-training-data-crawler
User-agent: Cotoyogi
User-agent: Crawl4AI
User-agent: Crawlspace
User-agent: Datenbank Crawler
User-agent: DeepSeekBot
User-agent: Devin
User-agent: Diffbot
User-agent: DuckAssistBot
User-agent: Echobot Bot
User-agent: EchoboxBot
User-agent: ExaBot
User-agent: FacebookBot
User-agent: facebookexternalhit
User-agent: Factset_spyderbot
User-agent: FirecrawlAgent
User-agent: FriendlyCrawler
User-agent: Gemini-Deep-Research
User-agent: Google-Agent
User-agent: Google-CloudVertexBot
User-agent: Google-Extended
User-agent: Google-Firebase
User-agent: Google-Gemini-CLI
User-agent: Google-NotebookLM
User-agent: GoogleAgent-Mariner
User-agent: GoogleOther
User-agent: GoogleOther-Image
User-agent: GoogleOther-Video
User-agent: GPTBot
User-agent: HenkBot
User-agent: iAskBot
User-agent: iaskspider
User-agent: iaskspider/2.0
User-agent: IbouBot
User-agent: ICC-Crawler
User-agent: ImagesiftBot
User-agent: imageSpider
User-agent: img2dataset
User-agent: ISSCyberRiskCrawler
User-agent: kagi-fetcher
User-agent: Kangaroo Bot
User-agent: KlaviyoAIBot
User-agent: KunatoCrawler
User-agent: laion-huggingface-processor
User-agent: LAIONDownloader
User-agent: LCC
User-agent: LinerBot
User-agent: Linguee Bot
User-agent: LinkupBot
User-agent: Manus-User
User-agent: meta-externalagent
User-agent: Meta-ExternalAgent
User-agent: meta-externalfetcher
User-agent: Meta-ExternalFetcher
User-agent: meta-webindexer
User-agent: MistralAI-User
User-agent: MistralAI-User/1.0
User-agent: MyCentralAIScraperBot
User-agent: NagetBot
User-agent: netEstate Imprint Crawler
User-agent: newsai
User-agent: NotebookLM
User-agent: NovaAct
User-agent: OAI-SearchBot
User-agent: omgili
User-agent: omgilibot
User-agent: OpenAI
User-agent: opencode
User-agent: Operator
User-agent: PanguBot
User-agent: Panscient
User-agent: panscient.com
User-agent: Perplexity-User
User-agent: PerplexityBot
User-agent: PetalBot
User-agent: PhindBot
User-agent: Poggio-Citations
User-agent: Poseidon Research Crawler
User-agent: QualifiedBot
User-agent: QuillBot
User-agent: quillbot.com
User-agent: SBIntuitionsBot
User-agent: Scrapy
User-agent: SemrushBot-OCOB
User-agent: SemrushBot-SWA
User-agent: ShapBot
User-agent: Sidetrade indexer bot
User-agent: Spider
User-agent: TavilyBot
User-agent: Terra Cotta
User-agent: TerraCotta
User-agent: Thinkbot
User-agent: TikTokSpider
User-agent: Timpibot
User-agent: Trae
User-agent: TwinAgent
User-agent: VelenPublicWebCrawler
User-agent: WARDBot
User-agent: Webzio-Extended
User-agent: webzio-extended
User-agent: wpbot
User-agent: WRTNBot
User-agent: YaK
User-agent: YandexAdditional
User-agent: YandexAdditionalBot
User-agent: YouBot
User-agent: ZanistaBot
Disallow: /

User-agent: *
Allow: /

Sitemap: https://emanuelpina.pt/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 38 entries Valid XML Yes
Sample URLs:
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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.emanuelpina.pt/
200https://emanuelpina.pt/

Preferred variant: non-www

HTTP → HTTPS

308http://emanuelpina.pt/ → https://emanuelpina.pt/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
emanuelpina.pt
PASS
emanuelpina.pt
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

Unknown

SSL certificate

53 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a01:4f8:c012:2a6b::1

Registrar

Registrar unknown

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Name Servers ns1.desec.io, ns2.desec.org
Hosting
IP Address 2a01:4f8:c012:2a6b::1
Data source: whois (1.6s)

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

Connection waterfall

DNS Lookup 42 ms TCP Connect 30 ms TLS Handshake 34 ms Server Processing 31 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