Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 748 ms totalREVIEW
https://tap.pt
56 ms · HTTP/1.1
https://www.flytap.com/
167 ms · HTTP/1.1
https://www.flytap.com/es-es
524 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://tap.pt | 301 | 56 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.flytap.com/ | 302 | 167 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.flytap.com/es-es | 200 | 524 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
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.
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.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# 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
BTLS Certificate Expiry & Recommendations65 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 131 ms lookupPASS
| A | 104.18.24.185, 104.18.25.185 |
| AAAA | — |
| CNAME | — |
| NS | ns3-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 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencetap.pt — hosted on CloudflarePASS
Unknown
65 days
Issued by Let's Encrypt
Unknown
Status unknown
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.18.25.185
Registrar unknown
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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