Skip to content

Hostname

mail.control.com.py

Last fetched

mail.control.com.py resolves to 52.116.55.215, announced in 52.116.0.0/18 by SOFTLAYER - IBM Cloud in US. mail.control.com.py 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.control.com.pyRouting diversity1.5/10Peering density8.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/mail.control.com.py

Resolution chain

IPv6 resolution

No AAAA record for mail.control.com.py is recorded in WhisperGraph.

Attribution

ibm

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mail.control.com.py. 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.prodominios.com
  • ns11.prodominios.com
  • ns12.prodominios.com
  • ns2.prodominios.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

  • control.com.py

SPF policy

  • include: sv2.prodominios.com
  • a: mail.control.com.py
  • mx: mail.control.com.py
  • ip: 173.193.3.131
  • ip: 52.116.55.212
  • ip: 52.116.55.214
  • ip: 52.116.55.215
  • ip: 52.117.30.9

Threat-feed evidence

History

Related pages

Pivot from mail.control.com.py 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.control.com.py"})-[: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.