Skip to content

Hostname

planet-cards.com

Last fetched

planet-cards.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. planet-cards.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 · planet-cards.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/planet-cards.com

Resolution chain

No IPv4 resolution is recorded for planet-cards.com in WhisperGraph.

IPv6 resolution

No AAAA record for planet-cards.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:81
Registrant organisation
groupe sprint
Contact emails
0447f267f4f02adde02fd0d9f34eca2d-3584177@contact.gandi.net, 39f41da0e4f4682669947fd47bfc695d-3584177@contact.gandi.net, 5d158742502416f9ba92a78b9162c2f1-3584177@contact.gandi.net, a5b4b331635330e556918f099498b8b4-3584177@contact.gandi.net, a64b12f27e393a2f158b506e871170c6-624292@contact.gandi.net, b95974388310d997c6ac4711e64c0b29-50594918@contact.gandi.net

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

  • ns-116-a.gandi.net
  • ns-149-b.gandi.net
  • ns-81-c.gandi.net
  • ns1.gandi.net

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • ip: 93.93.42.0/24
  • ip: 93.93.45.0/24
  • ip: 193.84.73.0/24
  • include: _spf.google.com
  • a: smtp.itinsell.com
  • include: mail.zendesk.com
  • include: spf.pvmailer.net
  • ip: 52.211.112.37
  • ip: 52.213.254.121
  • ip: 80.153.180.56

Threat-feed evidence

History

Related pages

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