Hostname
prospectresearchresources.com
Last fetched
prospectresearchresources.com resolves to 16.15.176.172, announced in 16.15.176.0/21 by AMAZON-AES - Amazon.com, Inc. in US. prospectresearchresources.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
- 16.15.176.172
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.176.82
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.179.2
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.231
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.187.171
16.15.184.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.194.120
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.195.40
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.207.141
16.15.200.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.218.253
16.15.216.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.223.213
16.15.216.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.223.245
16.15.216.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.182.105.85
16.182.96.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 16.182.108.61
16.182.96.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 16.182.69.45
16.182.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 16.182.71.85
16.182.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 16.182.73.149
16.182.72.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 16.182.98.149
16.182.96.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 3.5.16.224
3.5.16.0/24 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.216.216.13
52.216.208.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.216.49.245
52.216.48.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for prospectresearchresources.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:299
- Registrant organisation
- domain administrator
- Contact emails
- admin@wealthengine.com, domain-names@euromoneyplc.com
Company
Technology
prospectresearchresources.com has been observed using 11 technologies somewhere in its estate. This is observed use, not an exposure finding.
- Open Graph · content management system
- reCAPTCHA · captcha
- Amazon Web Services · cloud hosting
- Cart Functionality · e-commerce
- Choices · javascript libraries
- Squarespace · content management system
- Squarespace Commerce · e-commerce
- Stimulus · javascript frameworks
- Amazon S3 · content delivery network
- Amazon Route 53 · domain name services
- AMP · javascript frameworks
Subdomains
| Subdomain |
|---|
| www.prospectresearchresources.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for prospectresearchresources.com.
DKIM signing
No DKIM signing vendor is attributed to prospectresearchresources.com in WhisperGraph.
Nameservers
- ns-327.awsdns-40.com
- ns-865.awsdns-44.net
- ns-1326.awsdns-37.org
- ns-1965.awsdns-53.co.uk
Threat-feed evidence
History
Related pages
Pivot from prospectresearchresources.com into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap)
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.