Skip to content

Hostname

sigor.gov.py

Last fetched

sigor.gov.py resolves to 190.128.170.34, announced in 190.128.128.0/18 by AS23201 - Telecel S.A. in PY. sigor.gov.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 · sigor.gov.pyRouting diversity2.4/10Peering density7.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/sigor.gov.py

Resolution chain

IPv6 resolution

No AAAA record for sigor.gov.py is recorded in WhisperGraph.

Attribution

telecel

ORIGIN_AS

WHOIS identity

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

Subdomains

Subdomain
api.sigor.gov.py
mail.sigor.gov.py
ns.sigor.gov.py
test.sigor.gov.py
www.sigor.gov.py

Showing 5 of 5 subdomains (5 per page).

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

  • 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
  • inet2.telecel.com.py
  • inet3.telecel.com.py
  • ns3.telecel.com.py
  • ns.sigor.gov.py

MX records

  • smtprelay.tigo.com.py
  • mail.sigor.gov.py

SPF policy

  • ip: 192.168.80.0/24
  • a: sigor.gov.py
  • mx: sigor.gov.py
  • a: mail.sigor.gov.py

Threat-feed evidence

History

Related pages

Pivot from sigor.gov.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: "sigor.gov.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.