Skip to content

Hostname

feb.es

Last fetched

feb.es resolves to 193.46.238.167, announced in 193.46.238.0/24 by MEYTEL-AS - Meytel Publicidad S.L. in ES. feb.es 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 · feb.esRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.8/10canon.whisper.security/host/feb.es

Resolution chain

IPv6 resolution

No AAAA record for feb.es is recorded in WhisperGraph.

Attribution

meytel publicidad

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for feb.es. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

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

  • ns10.dnsmadeeasy.com
  • ns10.hosting-meytel.net
  • ns11.hosting-meytel.net
  • ns12.hosting-meytel.net
  • ns13.hosting-meytel.net
  • ns14.hosting-meytel.net
  • ns15.hosting-meytel.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

MX records

  • feb-es.mail.protection.outlook.com

SPF policy

  • ip: 148.105.0.0/16
  • ip: 198.2.128.0/18
  • ip: 205.201.128.0/20
  • include: amazonses.com
  • include: spf.protection.outlook.com
  • include: servers.mcsv.net

Threat-feed evidence

History

Related pages

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