Skip to content

Hostname

bitdefender.pt

Last fetched

bitdefender.pt resolves to 104.18.20.43, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. bitdefender.pt is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · bitdefender.ptRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint6.9/10canon.whisper.security/host/bitdefender.pt

Resolution chain

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrant organisation
3-082 null
Contact emails
domains-admin@bitdefender.com, bitdefender@safenames.net

Subdomains

Subdomain
ns4.bitdefender.pt
www.bitdefender.pt

Showing 2 of 2 subdomains (2 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • pdns210.ultradns.biz
  • pdns210.ultradns.com
  • a1-39.akam.net
  • a10-64.akam.net
  • a20-66.akam.net
  • a3-65.akam.net
  • a6-65.akam.net
  • a9-64.akam.net
  • pdns210.ultradns.net
  • pdns210.ultradns.org

MX records

  • mx11.bitdefender.com
  • mx12.bitdefender.com

SPF policy

  • include: spf.bitdefender.com
  • include: digitalrivercontent.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • include: _spf.atlassian.net
  • include: 341979.spf06.hubspotemail.net
  • include: spf.mindmatrix.net

Threat-feed evidence

History

Related pages

Pivot from bitdefender.pt into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "bitdefender.pt"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.