Hostname
corte.pro
Last fetched
corte.pro resolves to 31.177.76.32, announced in 31.177.76.0/24 by RU-CENTER - JSC "RU-CENTER" in RU. corte.pro 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
- 31.177.76.32
31.177.76.0/24 · RU-CENTER - JSC "RU-CENTER" · Moscow, RU
- 31.177.80.32
31.177.80.0/24 · RU-CENTER - JSC "RU-CENTER" · Moscow, RU
- 87.236.16.35
87.236.16.0/24 · BEGET-AS - Beget LLC · St Petersburg, RU
IPv6 resolution
No AAAA record for corte.pro is recorded in WhisperGraph.
Attribution
jsc ru center
ORIGIN_AS
WHOIS identity
- Registrar
- iana:463
- Registrant organisation
- ooo 'technoprom'
- Contact emails
- zakaz@worldtools.ru
Subdomains
| Subdomain |
|---|
| www.corte.pro |
Showing 1 of 1 subdomain (1 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.
Mail and authentication
Nameservers
- ns1.beget.com
- ns2.beget.com
- ns1.beget.pro
- ns2.beget.pro
- ns1.beget.ru
- ns2.beget.ru
- dnsproxy1.fm.nic.ru
- dnsproxy2.fm.nic.ru
MX records
- mx1.beget.ru
- mx2.beget.ru
- nomail.nic.ru
SPF policy
- redirect: beget.ru
Threat-feed evidence
History
Related pages
Pivot from corte.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: "corte.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.