Hostname
progrtb.com
Last fetched
progrtb.com resolves to 18.245.113.115, announced in 18.245.112.0/22 by AMAZON-02 - Amazon.com, Inc. in US. progrtb.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
- 18.245.113.115
18.245.112.0/22 · AMAZON-02 - Amazon.com, Inc. · Dallas, US
- 18.245.113.127
18.245.112.0/22 · AMAZON-02 - Amazon.com, Inc. · Dallas, US
- 18.245.113.24
18.245.112.0/22 · AMAZON-02 - Amazon.com, Inc. · Dallas, US
- 18.245.113.65
18.245.112.0/22 · AMAZON-02 - Amazon.com, Inc. · Dallas, US
- 54.239.195.113
54.239.195.0/24 · AMAZON-02 - Amazon.com, Inc. · Berlin, DE
- 54.239.195.122
54.239.195.0/24 · AMAZON-02 - Amazon.com, Inc. · Berlin, DE
- 54.239.195.25
54.239.195.0/24 · AMAZON-02 - Amazon.com, Inc. · Berlin, DE
- 54.239.195.96
54.239.195.0/24 · AMAZON-02 - Amazon.com, Inc. · Berlin, DE
- 65.8.131.106
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.122
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.47
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.95
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.54.111
65.8.48.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 65.8.54.18
65.8.48.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 65.8.54.24
65.8.48.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 65.8.54.3
65.8.48.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
IPv6 resolution
No AAAA record for progrtb.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
Subdomains
Mail and authentication
Nameservers
- ns-198.awsdns-24.com
- ns-769.awsdns-32.net
- ns-1259.awsdns-29.org
- ns-1671.awsdns-16.co.uk
Threat-feed evidence
History
Related pages
Pivot from progrtb.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: "progrtb.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.