Skip to content

Hostname

portaldelligue.com

Last fetched

portaldelligue.com resolves to 34.160.55.58, announced in 34.160.0.0/16 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. portaldelligue.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 · portaldelligue.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/portaldelligue.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Registrant organisation
c/o whoisproxy.com
Contact emails
86715c487d@portaldelligue.com.whoistrustee.com, 3d3796895849179d29e8f30e5591ec3c6d00826084a15dccf7a665685d6b35f7@portaldelligue.com.whoisproxy.org, 43e5e9d5453ef9b6e42ca0aab1dc92c2ff252e53f96b2c44b5eb1412009fa863@portaldelligue.com.whoisproxy.org, 798ae602340ba17d9609d792f009bbb619cefac0f099583f8ed72788ef7955c9@portaldelligue.com.whoisproxy.org, 9ed73d1e10fadf9a96864b4c367ea34641b3070d08d8104b73a385545b350c52@portaldelligue.com.whoisproxy.org

Subdomains

Mail and authentication

Nameservers

  • ns1.dnsimple.com
  • ns3.dnsimple.com
  • ns1.dnsimple-edge.com
  • ns3.dnsimple-edge.io
  • ns2.dnsimple-edge.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
  • ns4.dnsimple-edge.org

MX records

  • mx1.yieldingyak.com

SPF policy

  • include: spf.yieldingyak.com
  • include: 136224628.spf2.netcorecloud.net

Threat-feed evidence

History

Related pages

Pivot from portaldelligue.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: "portaldelligue.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.