Skip to content

Hostname

redinfor.com.pe

Last fetched

redinfor.com.pe resolves to 149.56.85.243, announced in 149.57.41.0/24 by OVH - OVH SAS in CA. redinfor.com.pe 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 · redinfor.com.peRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/redinfor.com.pe

Resolution chain

IPv6 resolution

No AAAA record for redinfor.com.pe is recorded in WhisperGraph.

Attribution

ovh

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:nic.pe
Registrant organisation
redinfor e.i.r.l.

Subdomains

Subdomain
autodiscover.redinfor.com.pe
cpanel.redinfor.com.pe
cpcalendars.redinfor.com.pe
cpcontacts.redinfor.com.pe
cursos.redinfor.com.pe
mail.redinfor.com.pe
webdisk.redinfor.com.pe
webmail.redinfor.com.pe
www.redinfor.com.pe

Showing 9 of 10. View all subdomains →

Web-graph footprint

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.hpserverdns.com
  • ns2.hpserverdns.com
  • 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

  • redinfor.com.pe

SPF policy

  • a: redinfor.com.pe
  • mx: redinfor.com.pe
  • ip: 142.44.222.227
  • ip: 149.56.85.244

Threat-feed evidence

History

Related pages

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