Skip to content

Hostname

mattelsa.net

Last fetched

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

Resolution chain

No IPv4 resolution is recorded for mattelsa.net in WhisperGraph.

IPv6 resolution

No AAAA record for mattelsa.net is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:81
Registrant organisation
jhon harold henao cardona
Contact emails
46be8bc38dfe7e636cddf3d959f3c9ff-19464241@contact.gandi.net, 498f557837666c98cc2d0c0f870815a9-4836487@contact.gandi.net, 4de206a8c70a0f415921d69e996a7b97-2658472@contact.gandi.net, 5f4201a8fd725425b2d760b444c4afa0-6323807@contact.gandi.net, a52805581217583b29d5bf0d026ea11d-19464241@contact.gandi.net, monicachu@mattelsa.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-509.awsdns-63.com
  • ns-656.awsdns-18.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
  • ns-1361.awsdns-42.org
  • ns-1657.awsdns-15.co.uk

MX records

  • mattelsa-net.mail.protection.outlook.com

SPF policy

  • include: spf.mailjet.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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