Skip to content
https://tap.pt

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
B
Redirect Chain
2 redirect(s), 748 ms total
REVIEW
2 redirect(s), 748 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.flytap.com/
Info::
Redirect overhead: 748 ms total
Got: 748 ms
Info::
Cross-domain redirect detected

https://tap.pt

56 ms · HTTP/1.1

301

https://www.flytap.com/

167 ms · HTTP/1.1

302

https://www.flytap.com/es-es

524 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tap.pt30156 msHTTP/1.1cloudflare
2https://www.flytap.com/302167 msHTTP/1.1cloudflare
3https://www.flytap.com/es-es200524 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 1738 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 1738 B Sitemaps referenced 0 User-agents meta-externalagent, CCBot, Google-Extended, GPTBot, *, Amazonbot, Applebot-Extended, Bytespider, ClaudeBot, CloudflareBrowserRenderingCrawler Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content


sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
65 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

65
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 & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9ece9a64bbb46f75-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9ece9a64bbb46f75-CDG
A+
DNS Records
2 A records, 131 ms lookup
PASS
2 A records, 131 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.24.185, 104.18.25.185
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns3-04.azure-dns.org, ns2-04.azure-dns.net, ns4-04.azure-dns.info, ns1-04.azure-dns.com
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: 131 ms
Got: 131 ms
A104.18.24.185, 104.18.25.185
AAAA
CNAME
NSns3-04.azure-dns.org, ns2-04.azure-dns.net, ns4-04.azure-dns.info, ns1-04.azure-dns.com
MX
10 tap-pt.mail.protection.outlook.com
TXT
atlassian-sending-domain-verification=faf669b3-b8de-4906-9581-7af685b991a1
v=verifydomain MS=ms49027728
jamf-site-verification=KMUPLnCUm8GUqv1xQ-GKXA
LoQM_QkPu1PDBSOu5WYsgkH-CZ_WGaqdMYpJTVsc4yY
globalsign-domain-verification=7D2nSAkiGVBRwdj0mAbgglLd09UkW6yuMSSxESK5cB
MS=ms10899566
ethiack-verification=8ac9343c4023fe0bfe1877e0d7baa231cd6581d8e14803753de9319f10d...
nj0m3cdtvgcg0mk3llv07c0bygj92f2g
tohoMibiOZe4i2/66uRo16PMpGaYsfCjvefR2OqC1PfYoEPig0NL6BF1YsqwYdK3IYrBexgqKYx1wZjB...
atlassian-domain-verification=dYjPFZAJMB38TQk7lFYJo5LrMuNuP/aVxahUbVsshNpsCsABpO...
globalsign-domain-verification=pE4wQeXXyNl2wvxfsvX6KmtTcEIG_QW5r98kx3cRHh
SPF v=spf1 ip4:91.198.90.0/24 ip4:194.65.18.210 ip4:194.65.18.212 ip4:195.219.250.22...
jamf-site-verification=X6Yt6AztmrBdCAs5B8OCpQ
onetrust-domain-verification=24956eaee24e4a39bd94fedfa510fc18
apple-domain-verification=pg5Sh38nGIb9Xcgm
google-site-verification=Z_5hnZnTxMcyygD0z0sFzG4SE4VjT27GYYA2hw7plJA
CAALookup not available with standard resolver
Resolved in 131 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+
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.tap.pt/
200https://tap.pt/

Preferred variant: non-www

HTTP → HTTPS

301http://tap.pt/ https://www.flytap.com/

Consistent

A+
Domain Intelligence
tap.pt — hosted on Cloudflare
PASS
tap.pt — hosted on Cloudflare
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: Cloudflare
Got: AS13335
Domain expiry

Unknown

SSL certificate

65 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.25.185

Registrar

Registrar unknown

Unlocked 4 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-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net, ns3-04.azure-dns.org
Hosting
IP Address 104.18.25.185
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: whois (1.7s)

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

Connection waterfall

DNS Lookup 71 ms TCP Connect 16 ms TLS Handshake 22 ms Server Processing 18 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