Hostname
2guyscolo.com
Last fetched
2guyscolo.com resolves to 199.79.190.10, announced in 199.79.190.0/24 by LOGIXCOMM-AS4 - Logix in US. 2guyscolo.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 199.79.190.10
199.79.190.0/24 · LOGIXCOMM-AS4 - Logix · McKinney, US
IPv6 resolution
No AAAA record for 2guyscolo.com is recorded in WhisperGraph.
Attribution
logix
ORIGIN_AS
WHOIS identity
- Registrar
- iana:93
- Registrant organisation
- gkg.net domain proxy service
- Contact emails
- 132c31e8e6eda9074c27d9f7748273d44cc4762f@privatedomain.gkg.net, 142319f66b10e72b5c6217d9a0290b7c6ec5c465@privatedomain.gkg.net, 20c1ab6db52f8ddd3190bd05ffaf1bc2ed2ce95b@privatedomain.gkg.net, 394d0de9f14dc07673f7d6746df3797391497b86@privatedomain.gkg.net, 3d07c4f5ffc5f4e914b754628689eb18d8e1d606@privatedomain.gkg.net, 88e0c5e47b25d43acfb9449241c7ab506d3bf978@privatedomain.gkg.net, 97e6adef6f5e10434a4f610c30605886410c5a93@privatedomain.gkg.net, a2d941d89cddbfd083757950f42182bac395c8b8@privatedomain.gkg.net, a68f35fc0107fbf9ba5d18d3a8468162ab373116@privatedomain.gkg.net, aaef30374c204542bd06bc2935aca1c34ac893ee@privatedomain.gkg.net, b5304ffe9d4fe9efccdf6f9ebbe5907cfd197b6c@privatedomain.gkg.net, f7fb304a701b6a2eb2e746221dee9b4ae149c366@privatedomain.gkg.net
Subdomains
| Subdomain |
|---|
| bsg.2guyscolo.com |
| crm.2guyscolo.com |
| mail.2guyscolo.com |
| ns1.2guyscolo.com |
| ns2.2guyscolo.com |
| ns3.2guyscolo.com |
Showing 6 of 6 subdomains (6 per page).
Mail and authentication
Nameservers
- ns1.2guyscolo.com
- ns2.2guyscolo.com
- ns1.intosh.com
MX records
- mail.2guyscolo.com
SPF policy
- a: 2guyscolo.com
- mx: 2guyscolo.com
- a: mail.2guyscolo.com
- ip: 199.79.190.3
Threat-feed evidence
History
Related pages
Pivot from 2guyscolo.com 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: "2guyscolo.com"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.