Skip to content

Hostname

secop.gov.co

Last fetched

secop.gov.co resolves to 20.75.102.234, announced in 20.64.0.0/10 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. secop.gov.co 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 · secop.gov.coRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/secop.gov.co

Resolution chain

IPv6 resolution

No AAAA record for secop.gov.co is recorded in WhisperGraph.

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for secop.gov.co. 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
community.secop.gov.co
formacion.secop.gov.co
mail.secop.gov.co
marketplace-formacion.secop.gov.co
preproduccion.secop.gov.co
relay.secop.gov.co
smtp.secop.gov.co
subastas-formacion.secop.gov.co
subastas-preproduccion.secop.gov.co
subastas.secop.gov.co
wiki.secop.gov.co
www.secop.gov.co

Showing 12 of 12 subdomains (12 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

  • ns1-08.azure-dns.com
  • ns4-08.azure-dns.info
  • ns2-08.azure-dns.net
  • ns3-08.azure-dns.org

MX records

  • secop-gov-co.mail.protection.outlook.com

SPF policy

  • ip: 200.91.200.67/32
  • a: smtp.secop.gov.co
  • include: spf.protection.outlook.com
  • ip: 135.119.144.9
  • ip: 20.69.211.132
  • ip: 200.24.63.251

Threat-feed evidence

History

Related pages

Pivot from secop.gov.co 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: "secop.gov.co"})-[: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.