Hostname
coresystems.net
Last fetched
coresystems.net resolves to 108.131.231.23, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. coresystems.net 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
- 108.131.231.23
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.200.192.53
18.200.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.202.190.118
18.202.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.202.50.62
18.202.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.203.124.171
18.202.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 3.255.12.111
3.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.247.145.127
34.240.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.249.78.245
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.251.220.43
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.252.84.189
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 46.51.133.213
46.51.128.0/18 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.19.142.183
52.18.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.210.244.159
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.211.76.121
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.31.165.42
52.30.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.51.6.217
52.48.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.217.231.108
54.216.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.217.46.137
54.216.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.220.231.13
54.220.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 54.229.254.14
54.229.128.0/17 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
IPv6 resolution
No AAAA record for coresystems.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:151
- Registrant organisation
- coresystems
- Contact emails
- it@coresystems.ch, hostmaster@sap.com, info@coresystems.net, owner-3114079@coresystems.net.whoisprivacyservice.org, owner-3311461@coresystems.net.whoisprivacyservice.org, owner-8580593@coresystems.net.whoisprivacyservice.org
Company
- Company
- coresystems ag
Technology
coresystems ag has been observed using 38 technologies somewhere in its estate. This is observed use, not an exposure finding. The 20 most widely adopted:
- jQuery · javascript libraries
- Google Fonts API · font scripts
- Font Awesome · font scripts
- Google Analytics · intelligence and analytics
- Bootstrap · software framework
- Facebook · social media analytics and monitoring
- React · javascript frameworks
- Facebook Pixel · analytics
- YouTube · online community software
- Webpack · build automation
- RequireJS · javascript frameworks
- Adobe Fonts · web fonts
- Twitter · widgets
- Moment.js · javascript libraries
- LinkedIn · online community software
- Google Plus · widgets
- HubSpot · email marketing
- AngularJS · javascript frameworks
- Material Design Lite · ui frameworks
- Adobe Creative Suite · design
Peer companies
Subdomains
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
DNSSEC
WhisperGraph records no DNSSEC signature for coresystems.net.
DKIM signing
No DKIM signing vendor is attributed to coresystems.net in WhisperGraph.
Nameservers
- ns-242.awsdns-30.com
- ns-632.awsdns-15.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1039.awsdns-01.org
- ns-1836.awsdns-37.co.uk
MX records
- coresystems-net.mail.protection.outlook.com
SPF policy
- include: spf.coresuite.com
- include: _spf.sap.com
- include: mail.zendesk.com
- mx: coresystems.net
Threat-feed evidence
History
Related pages
Pivot from coresystems.net 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.