Skip to content

Hostname

mail.regor.pro

Last fetched

mail.regor.pro resolves to 217.181.161.223, announced in 217.181.128.0/17 by SEWAN-FR - SEWAN SAS in FR. mail.regor.pro 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 · mail.regor.proRouting diversity1.5/10Peering density5.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/mail.regor.pro

Resolution chain

IPv6 resolution

No AAAA record for mail.regor.pro is recorded in WhisperGraph.

Attribution

sewan

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mail.regor.pro. 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.

Mail and authentication

Nameservers

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

  • vade-mx-eu-fallback01.hornetsecurity.com
  • vade-mx-eu-fallback02.hornetsecurity.com
  • vade-mx-fr01.hornetsecurity.com
  • vade-mx-fr02.hornetsecurity.com

SPF policy

  • include: spf.hornetsecurity.com
  • include: spf.protection.outlook.com
  • include: spf.sendinblue.com
  • include: mail.easyw3.net
  • include: srvw3-130.easyw3.net
  • a: mail.regor.pro
  • mx: mail.regor.pro
  • ip: 185.42.179.248
  • ip: 217.181.161.223

Threat-feed evidence

History

Related pages

Pivot from mail.regor.pro 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: "mail.regor.pro"})-[: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.