Skip to content

Hostname

bitdefender.it

Last fetched

bitdefender.it resolves to 104.18.37.87, announced in 104.18.37.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. bitdefender.it 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.itRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint9.2/10canon.whisper.security/host/bitdefender.it

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:eurodns sa
Registrant organisation
bitdefender ipr management

Subdomains

Subdomain
resellerportal.bitdefender.it
www.bitdefender.it

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
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • pdns210.ultradns.net
  • pdns210.ultradns.org

MX records

  • mx01.bitdefender.com
  • mx02.bitdefender.com

SPF policy

  • include: spf.bitdefender.com
  • include: spf.protection.outlook.com
  • a: bitdefender.it
  • mx: bitdefender.it
  • include: 341979.spf06.hubspotemail.net
  • include: spf.mindmatrix.net

Threat-feed evidence

History

Related pages

Pivot from bitdefender.it 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.it"})-[: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.