Skip to content

Hostname

pkfbofidi.com

Last fetched

pkfbofidi.com resolves to 188.208.37.81, announced in 188.208.36.0/23 by COMBELL-AS - Combell NV in BE. pkfbofidi.com 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 · pkfbofidi.comRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.0/10canon.whisper.security/host/pkfbofidi.com

Resolution chain

IPv6 resolution

No AAAA record for pkfbofidi.com is recorded in WhisperGraph.

Attribution

combell

ORIGIN_AS

WHOIS identity

Registrar
iana:1467
Contact emails
info@domain-contact.org

Subdomains

Web-graph footprint

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

Mail and authentication

Nameservers

  • ns1.combell.eu
  • ns3.combell.net
  • ns4.combell.net

MX records

  • pkfbofidi-com.b-v1.mx.microsoft

SPF policy

  • ip: 13.36.253.151/32
  • ip: 13.37.17.159/32
  • ip: 35.181.156.191/32
  • ip: 84.199.87.192/28
  • ip: 3.123.206.219/32
  • ip: 15.236.171.222/32
  • ip: 213.224.20.34/32
  • ip: 213.224.39.41/32
  • ip: 3.68.129.51/32
  • include: spf.protection.outlook.com
  • include: spf.sendinblue.com
  • a: mail.twikey.com
  • include: spf.flexmail.eu
  • include: spf.icontroller.eu
  • include: spf.eu.exclaimer.net
  • include: servers.mcsv.net
  • include: yukiworks.nl
  • ip: 178.132.11.207
  • ip: 188.118.15.200
  • ip: 188.118.16.203
  • ip: 188.118.19.195
  • ip: 188.118.38.189
  • ip: 188.118.45.117
  • ip: 188.118.45.118
  • ip: 188.118.54.177
  • ip: 188.118.54.182
  • ip: 193.58.112.122
  • ip: 81.82.204.11
  • ip: 94.140.177.5
  • ip: 94.140.180.147
  • ip: 94.140.189.139
  • ip: 94.140.190.48
  • ip: 94.226.218.21

Threat-feed evidence

History

Related pages

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